Provisioning for smart navigation services

ABSTRACT

Techniques for provisioning a smart navigation service are presented. The provisioning can be performed by a name owner, by the smart navigation service itself, or by a third-party keyword service. The provisioned information can include an entity name, a keyword, and possibly other data correlated to at least one network locator. The navigation service electronically stores in navigation service persistent memory a rule correlating the entity name, the keyword, and, if used, the other data, to the at least one network locator, such that when the navigation service receives, from a client computer communicatively coupled to the navigation service, command data that includes the entity name, the keyword, and possibly other data, the navigation service responds to the client computer with the at least one network locator.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. ProvisionalPatent Application No. 62/041,384 filed Aug. 25, 2014 and entitled,“Keyword Services for Smart Navigation”.

This application is a continuation-in-part of, and claims priority toand the benefit of, pending U.S. patent application Ser. No. 14/176,723filed Feb. 10, 2014 and entitled, “Smart Navigation Services”.

U.S. patent application Ser. No. 14/176,723 filed Feb. 10, 2014 andentitled, “Smart Navigation Services” is a continuation-in-part of, andclaims priority to and the benefit of pending U.S. patent applicationSer. No. 13/250,864 filed Sep. 30, 2011 and entitled, “Methods andSystems for Providing Content Provider-Specified URL KeywordNavigation”, which claims the benefit of U.S. Provisional ApplicationNo. 61/452,516 filed Mar. 14, 2011, the disclosures of which are herebyincorporated by reference herein in their entireties.

U.S. patent application Ser. No. 14/176,723 filed Feb. 10, 2014 andentitled, “Smart Navigation Services” is also a continuation-in-part of,and claims priority to and the benefit of pending U.S. patentapplication Ser. No. 13/622,541 filed Sep. 19, 2012 and entitled,“Methods and Systems for Providing Content Provider-Specified URLKeyword Navigation”, which is a continuation-in-part of U.S. patentapplication Ser. No. 13/250,864 filed Sep. 30, 2011, which claims thebenefit of U.S. Provisional Application No. 61/452,516 filed Mar. 14,2011, the disclosures of which are hereby incorporated by referenceherein in their entireties.

U.S. patent application Ser. No. 14/176,723 filed Feb. 10, 2014 andentitled, “Smart Navigation Services” also claims the benefit of pendingU.S. Provisional Patent Application No. 61/809,377 filed Apr. 7, 2013and entitled, “Desired Resource Navigation”, pending U.S. ProvisionalPatent Application No. 61/811,234 filed Apr. 12, 2013 and entitled,“Desired Resource Navigation”, and pending U.S. Patent Application No.61/820,391 filed May 7, 2013, and entitled, “Smart Navigation in GeneralName Spaces”, the disclosures of which are hereby incorporated byreference herein in their entireties.

SUMMARY

According to various embodiments, a method of provisioning, by a keywordservice and on behalf of a name owner, a navigation service, isdisclosed. The method includes receiving, over a computer network, anelectronic authorization to provision the navigation service with atleast one network locator in association with both the keyword and anentity name associated with the name owner; and providing to thenavigation service, over a computer network, at least one rulecorrelating at least the keyword and the entity name to the at least onenetwork locator; such that the navigation service electronically storesthe at least one rule in navigation service persistent memory, such thatwhen the navigation service receives, from a client computercommunicatively coupled to the navigation service, command dataincluding the entity name and the keyword, the navigation serviceresponds to the client computer with the at least one network locator.

Various optional features of the above embodiments include thefollowing. The receiving the electronic authorization may includereceiving the electronic authorization from the name owner or from thekeyword service. The at least one network locator may include a uniformresource locator (URL). The navigation service may not be a domain namesystem (DNS) service. The method may include soliciting the name ownerto provision at least one network locator in association with both thekeyword and the entity name, where the soliciting includes sending anelectronic message over a computer network to the name owner. Theelectronic message may include a recommended network locator. The methodmay include receiving, over a computer network, multiple electronicauthorizations of respective name owners to provision respective atleast one network locators in association with the keyword andrespective entity names; and providing to the navigation service, over acomputer network, respective at least one rules correlating the keywordand the respective entity names to the respective at least one networklocators. The command data may be derived from a command string providedto the client computer, the command string consisting of a name portionand a keyword portion, where the name portion includes the name and aname space identifier abutting the name, and where the keyword portionincludes the keyword. The keyword portion may further include a keyworddelimiter abutting the keyword, where the keyword delimiter is selectedfrom the group consisting of: #, !, “.”, $, and |, and where the namespace identifier is selected from the group consisting of @, fb, in, and“.”. The method may include receiving monetary compensation from thename owner in exchange for the providing. The at least one rule maycorrelate the keyword, the entity name, and other data to the at leastone network locator; such that the navigation service electronicallystores the at least one rule in persistent memory, such that when thenavigation service receives, from a client computer, command dataincluding the entity name, the keyword, and the other data, thenavigation service responds with the at least one network locator. Theother data may include geolocation data. The other data may include dataidentifying a language. The at least one rule may specify a databasequery.

According to various embodiments, a method of a navigation service beingprovisioned by a keyword service and on behalf of a name owner isdisclosed. The method includes receiving, over a computer network, anelectronic authorization to provision the navigation service with atleast one network locator in association with a keyword and an entityname associated with the name owner; receiving, from the keywordservice, by the navigation service, and over a computer network, atleast one rule correlating at least the keyword and the entity name tothe at least one network locator; electronically storing the at leastone rule in navigation service persistent memory; receiving, from aclient computer communicatively coupled to the navigation service overthe computer network, command data including the entity name and thekeyword; applying the at least one rule to the command data to obtainthe at least one network locator; and providing, over the computernetwork, the client computer with the at least the network locator.

Various optional features of the above embodiments include thefollowing. The receiving the electronic authorization may includereceiving the electronic authorization from the name owner or thekeyword service. The at least one network locator may include a uniformresource locator (URL). The navigation service may not be a domain namesystem (DNS) service. The method may include soliciting the name ownerto authorize the keyword service to provision the navigation service.The soliciting may include sending an electronic message over thecomputer network to the name owner. The method ma include receiving,over a computer network, multiple electronic authorizations ofrespective name owners to provision respective at least one networklocators in association with the keyword and respective entity names;and receiving, from the keyword service, by the navigation service, andover a computer network, respective at least one rules correlating thekeyword and the respective entity names to the respective at least onenetwork locators. The command data may be derived from a command stringprovided to the client computer, the command string consisting of a nameportion and a keyword portion, where the name portion includes the nameand a name space identifier abutting the name, and where the keywordportion includes the keyword. The keyword portion may further include akeyword delimiter abutting the keyword, where the keyword delimiter isselected from the group consisting of: #, !, “.”, $, and |, and wherethe name space identifier is selected from the group consisting of @,fb, in, and “.”. The method may include providing monetary compensationto the keyword service for the receiving the electronic association. Themethod may include electronically storing in the navigation servicepersistent memory at least one rule correlating at least one examplenetwork locator to an example keyword and the entity name. The methodmay include providing an electronic interface to the name owner;receiving, from the name owner over the computer network and through theelectronic interface, an electronic association of an additional atleast one network locator, an additional keyword, and the entity name;and electronically storing in the navigation service persistent memoryan additional at least one rule correlating the additional keyword andthe entity name to the at least one network locator. The at least onerule correlating at least the keyword and the entity name to the atleast one network locator may correlate the keyword, the entity name,and other data to the at least one network locator, and where thereceiving command data may include receiving command data including theentity name, the keyword, and the other data. The other data may includegeolocation data. The other data may include data identifying alanguage. The at least one rule may specify a database query.

According to various embodiments, a method of a navigation service beingprovisioned is disclosed. The method includes receiving, over a computernetwork, an electronic authorization of the name owner to provision thenavigation service with at least one network locator in association witha keyword, an entity name associated with the name owner, and otherdata; obtaining the at least one network locator, the keyword, and theother data; electronically storing in navigation service persistentmemory at least one rule correlating at least the entity name, thekeyword, and the other data to the at least one network locator;receiving, from a client computer communicatively coupled to thenavigation service over the computer network, command data including theentity name, the keyword, and the other data; applying the at least onerule to the command data to obtain the at least one network locator; andproviding, over the computer network, the client computer with the atleast one network locator.

Various optional features of the above embodiments include thefollowing. The obtaining may include generating. The method may includeproviding an electronic interface to the name owner; and the obtainingmay include obtaining, from the name owner over the computer network andthrough the electronic interface, the at least one network locator, thekeyword, and the other data. The other data may include geolocationdata. The other data may include data identifying a language. Thereceiving the electronic authorization may include receiving theelectronic authorization from the name owner. The at least one networklocator may include a uniform resource locator (URL). The navigationservice is not a domain name system (DNS) service. The method mayinclude receiving, over a computer network, multiple electronicauthorizations of respective name owners to provision respective atleast one network locators in association with the keyword, respectiveentity names, and respective other data; and electronically storing innavigation service persistent memory respective at least one rulescorrelating the keyword, the respective entity names, and the respectiveother data to the respective at least one network locators. The commanddata may be derived from a command string provided to the clientcomputer, the command string consisting of a name portion and a keywordportion, where the name portion includes the entity name and a namespace identifier abutting the entity name, and where the keyword portionincludes the keyword. The keyword portion may further include a keyworddelimiter abutting the keyword, where the keyword delimiter is selectedfrom the group consisting of: #, !, “.”, $, and |, and where the namespace identifier is selected from the group consisting of @, fb, in, and“.”. The other data may be provided to the client computer through auser interface, where the command data is further derived from the otherdata. The method may include electronically storing at least one examplenetwork locator in the navigation service persistent memory inassociation with an example keyword and the entity name. The at leastone rule may specify a database query.

According to various embodiments, a method of provisioning a keywordservice and a navigation service is disclosed. The method includesreceiving, over a computer network, an electronic authorization toprovision the keyword service with at least one network locator inassociation with a keyword, an entity name associated with the nameowner, and other data; electronically storing in keyword servicepersistent memory at least one rule correlating at least the entity nameand the other data to the at least one network locator; providing to thenavigation service, over a computer network, a network locator for thekeyword service; receiving, over a computer network and at the networklocator for the keyword service, command data including the entity nameand the other data; and responding to the command data, over a computernetwork, with information including the at least one network locator.

Various optional features of the above embodiments include thefollowing. The other data may include geolocation data. The other datamay include data identifying a language. The receiving the command datamay include receiving the command data from the navigation service; andthe responding to the command data may include responding to thenavigation service. The receiving the command data may include receivingthe command data from a client computer; and the responding to thecommand data may include responding to the client computer; such thatthe navigation service provides the network locator for the keywordservice to the client computer. The receiving the command data mayinclude receiving the command data and a client computer identifier fromthe navigation service; and the responding to the command data mayinclude responding to the client computer. The command data may bederived from a command string provided to the client computer, thecommand string consisting of a name portion and a keyword portion, wherethe name portion includes the name and a name space identifier abuttingthe name, and where the keyword portion includes the keyword. Thekeyword portion may further include a keyword delimiter abutting thekeyword, where the keyword delimiter is selected from the groupconsisting of: #, !, “.”, $, and |, and where the name space identifieris selected from the group consisting of @, fb, in, and “.”. The otherdata may be provided to the client computer through a user interface,where the command data is further derived from the other data. Thereceiving the electronic authorization may include receiving theelectronic authorization from the name owner or from the navigationservice. The at least one network locator may include a uniform resourcelocator (URL). The navigation service may not be a domain name system(DNS) service. The method may include soliciting the name owner toprovision at least one network locator in association with the keywordand the entity name, where the soliciting include sending an electronicmessage over a computer network to the name owner. The electronicmessage may include a recommended network locator. The method mayinclude receiving, over a computer network, multiple electronicauthorizations of respective name owners to provision respective atleast one network locators in association with the keyword andrespective entity names; and electronically storing in keyword servicepersistent memory respective at least one rules correlating at least therespective entity names to the respective at least one network locators.The at least one rule may specify a database query. The at least onerule correlating at least the entity name and the other data to the atleast one network locator may correlate the keyword, the entity name,and the other data to the at least one network locator, and the commanddata may further include the keyword.

According to various embodiments, a method of provisioning a navigationservice is disclosed. The method includes receiving, over a computernetwork, an electronic authorization to resolve command data including akeyword, an entity name associated with a name owner, and other data toat least one network locator using a keyword service, such that thekeyword service stores in keyword service persistent memory at least onerule correlating at least the entity name and the other data to the atleast one network locator; obtaining a network locator for the keywordservice; receiving, over a computer network and from a client computer,command data including the entity name and the other data; andproviding, over a computer network, a response to the command data, suchthat the client computer obtains the at least one network locator.

Various optional features of the above embodiments include thefollowing. The client computer may obtain the at least one networklocator from the navigation service, where the method may furtherinclude: providing, over a computer network and to the keyword service,at least the entity name and the other data, such that the keywordservice correlates at least the entity name and the other data to the atleast one network locator; and obtaining, over a computer network andfrom the keyword service, the at least one network locator; where theproviding, over the computer network, the response to the command data,includes providing the at least one network locator to the clientcomputer. The client computer may obtain the at least one networklocator from the keyword service, where the method may further include:correlating the entity name and the keyword to the network locator forthe keyword service; and where the providing, over the computer network,the response to the command data includes providing the network locatorfor the keyword service to the client computer; such that the clientcomputer provides at least the entity name and the other data to thekeyword service, such that the keyword service correlates the entityname and the other data to the at least one network locator, such thatthe client computer receives the at least one network locator from thekeyword service. The client may obtain the at least one network locatorfrom the keyword service, where the providing, over the computernetwork, the response to the command data includes providing at leastthe entity name, the other data, and an identifier of the clientcomputer to the keyword service, such that the keyword servicecorrelates at least the entity name and the other data to the at leastone network locator and provides the at least one network locator to theclient computer using the identifier of the client computer. The otherdata may include geolocation data. The other data may include dataidentifying a language. The command data may be derived from a commandstring provided to the client computer, the command string consisting ofa name portion and a keyword portion, where the name portion includesthe name and a name space identifier abutting the name, where thekeyword portion includes the keyword. The keyword portion may furtherinclude a keyword delimiter abutting the keyword, where the keyworddelimiter is selected from the group consisting of: #, !, “.”, $, and |,and where the name space identifier is selected from the groupconsisting of @, fb, in, and “.”. The other data may be provided to theclient computer through a user interface, where the command data isfurther derived from the other data. The receiving the electronicauthorization may include receiving the electronic authorization fromthe name owner or from the keyword service. The at least one networklocator may include a uniform resource locator (URL). The navigationservice may not be a domain name system (DNS) service. The method mayinclude electronically storing at least one rule in navigation servicepersistent memory correlating an example keyword and the entity name toat least one example network locator. The at least one rule may specifya database query. The at least one rule that correlates at least theentity name and the other data to the at least one network locatorfurther correlates the keyword, the entity name, and the other data tothe at least one network locator, where the command data furtherincludes the keyword.

According to various embodiments, a system for provisioning, by akeyword service and on behalf of a name owner, a navigation service, isdisclosed. The system includes: at least one keyword service servercomputer communicatively coupled to a computer network and configured toreceive, over a computer network, an electronic authorization toprovision the navigation service with at least one network locator inassociation with both the keyword and an entity name associated with thename owner; and provide to at least one navigation service servercomputer of the navigation service, over a computer network, at leastone rule correlating at least the keyword and the entity name to the atleast one network locator; such that the navigation serviceelectronically stores the at least one rule in navigation servicepersistent memory, such that when the navigation service receives, froma client computer communicatively coupled to the navigation service,command data including the entity name and the keyword, the navigationservice responds to the client computer with the at least one networklocator.

Various optional features of the above embodiments include thefollowing. The electronic authorization may be sent from the name owneror from the keyword service. The at least one network locator mayinclude a uniform resource locator (URL). The navigation service may notbe a domain name system (DNS) service. The keyword service may furtherbe configured to solicit the name owner to provision at least onenetwork locator in association with both the keyword and the entity nameby sending an electronic message over a computer network to the nameowner. The electronic message may include a recommended network locator.The at least one keyword service server computer may be furtherconfigured to receive, over a computer network, multiple electronicauthorizations of respective name owners to provision respective atleast one network locators in association with the keyword andrespective entity names, and provide to the navigation service, over acomputer network, respective at least one rules correlating the keywordand the respective entity names to the respective at least one networklocators. The command data may be derived from a command string providedto the client computer, the command string consisting of a name portionand a keyword portion, where the name portion includes the name and aname space identifier abutting the name, where the keyword portionincludes the keyword. The keyword portion may further include a keyworddelimiter abutting the keyword, where the keyword delimiter is selectedfrom the group consisting of: #, !, “.”, $, and |, and where the namespace identifier is selected from the group consisting of @, fb, in, and“.”. The keyword service may receive monetary compensation from the nameowner in exchange for providing the at least one rule. The at least onerule may correlate the keyword, the entity name, and other data to theat least one network locator; such that the navigation serviceelectronically stores the at least one rule in navigation servicepersistent memory, such that when the navigation service receives, froma client computer, command data including the entity name, the keyword,and the other data, the navigation service responds with the at leastone network locator. The other data may include geolocation data. Theother data may include data identifying a language. The at least onerule may specify a database query.

According to various embodiments, a system for a navigation servicebeing provisioned by a keyword service and on behalf of a name owner isdisclosed. The system includes at least one navigation service servercomputer communicatively coupled to a computer network and configured toreceive, over a computer network, an electronic authorization toprovision the navigation service with at least one network locator inassociation with a keyword and an entity name associated with the nameowner; receive, from the keyword service, by the navigation service, andover a computer network, at least one rule correlating at least thekeyword and the entity name to the at least one network locator;electronically store the at least one rule in navigation servicepersistent memory; receive, from a client computer communicativelycoupled to the navigation service over the computer network, commanddata including the entity name and the keyword; apply the at least onerule to the command data to obtain the at least one network locator; andprovide, over the computer network, the client computer with the atleast the network locator.

Various optional features of the above embodiments include thefollowing. The at least one navigation service server computer mayreceive the electronic authorization from the name owner or the keywordservice. The at least one network locator may include a uniform resourcelocator (URL). The navigation service may not be a domain name system(DNS) service. The at least one navigation service server computer maybe configured to solicit the name owner to authorize the keyword serviceto provision the navigation service. The at least one navigation serviceserver computer may solicit the name owner by sending an electronicmessage over the computer network to the name owner. The at least onenavigation service server computer may be configured to receive, over acomputer network, multiple electronic authorizations of respective nameowners to provision respective at least one network locators inassociation with the keyword and respective entity names; and receive,from the keyword service, over a computer network, respective at leastone rules correlating the keyword and the respective entity names to therespective at least one network locators. The command data may bederived from a command string provided to the client computer, thecommand string consisting of a name portion and a keyword portion, wherethe name portion includes the name and a name space identifier abuttingthe name, and where the keyword portion includes the keyword. Thekeyword portion may further include a keyword delimiter abutting thekeyword, where the keyword delimiter is selected from the groupconsisting of: #, !, “.”, $, and |, and where the name space identifieris selected from the group consisting of @, fb, in, and “.”. Thenavigation service may provide monetary compensation to the keywordservice for receiving the electronic association. The system may includenavigation service persistent memory storing at least one rulecorrelating at least one example network locator to an example keywordand the entity name. The system may further include an electronicinterface accessible by the name owner and configured to receive, fromthe name owner, over the computer network, and through the electronicinterface, an electronic association of an additional at least onenetwork locator, an additional keyword, and the entity name; where thenavigation service persistent memory is configured to store anadditional at least one rule correlating the additional keyword and theentity name to the at least one network locator. The at least one rulemay correlate the keyword, the entity name, and other data to the atleast one network locator, and the command data may include the entityname, the keyword, and the other data. The other data may includegeolocation data. The other data may include data identifying alanguage. The at least one rule may specify a database query.

According to various embodiments, a system for provisioning a navigationservice is disclosed. The system includes at least one navigationservice server computer configured to receive, over a computer network,an electronic authorization of the name owner to provision thenavigation service with at least one network locator in association witha keyword, an entity name associated with the name owner, and otherdata; obtain the at least one network locator, the keyword, and theother data; electronically store in navigation service persistent memoryat least one rule correlating at least the entity name, the keyword, andthe other data to the at least one network locator; receive, from aclient computer communicatively coupled to the navigation service overthe computer network, command data including the entity name, thekeyword, and the other data; apply the at least one rule to the commanddata to obtain the at least one network locator; and provide, over thecomputer network, the client computer with the at least one networklocator.

Various optional features of the above embodiments include thefollowing. The at least one navigation service server computer mayobtain the at least one network locator, the keyword, and the other databy generating the at least one network locator, the keyword, and theother data. The system may further include an electronic interfaceaccessible by the name owner; where the at least one navigation serviceserver computer obtains, from the name owner over the computer networkand through the electronic interface, the at least one network locator,the keyword, and the other data. The other data may include geolocationdata. The other data may include data identifying a language. The atleast one navigation service server computer may receive the electronicauthorization from the name owner. The at least one network locator mayinclude a uniform resource locator (URL). The navigation service may notbe a domain name system (DNS) service. The at least one navigationservice server computer may be further configured to receive, over acomputer network, multiple electronic authorizations of respective nameowners to provision respective at least one network locators inassociation with the keyword, respective entity names, and respectiveother data; and electronically store in navigation service persistentmemory respective at least one rules correlating the keyword, therespective entity names, and the respective other data to the respectiveat least one network locators. The command data may be derived from acommand string provided to the client computer, the command stringconsisting of a name portion and a keyword portion, where the nameportion includes the entity name and a name space identifier abuttingthe entity name, and where the keyword portion includes the keyword. Thekeyword portion may further include a keyword delimiter abutting thekeyword, where the keyword delimiter is selected from the groupconsisting of: #, !, “.”, $, and |, and where the name space identifieris selected from the group consisting of @, fb, in, and “.”. The otherdata may be provided to the client computer through a user interface,and the command data may be further derived from the other data. Thenavigation service persistent memory may electronically store at leastone example network locator in association with an example keyword andthe entity name. The at least one rule may specify a database query.

According to various embodiments, a system for provisioning a keywordservice and a navigation service is disclosed. The system includes atleast one keyword service server computer communicatively coupled to acomputer network and configured to receive, over a computer network, anelectronic authorization to provision the keyword service with at leastone network locator in association with a keyword, an entity nameassociated with the name owner, and other data; electronically store inkeyword service persistent memory at least one rule correlating at leastthe entity name and the other data to the at least one network locator;provide to the navigation service, over a computer network, a networklocator for the keyword service; receive, over a computer network and atthe network locator for the keyword service, command data including theentity name and the other data; and respond to the command data, over acomputer network, with information including the at least one networklocator.

Various optional features of the above embodiments include thefollowing. The other data may include geolocation data. The other datamay include data identifying a language. The at least one keywordservice server computer may receive the command data from the navigationservice; and the at least one keyword service server computer mayrespond to the command data by responding to the navigation service withthe information including the at least one network locator. The at leastone keyword service server computer may the command data from a clientcomputer; and the at least one keyword service server computer mayrespond to the command data by responding to the client computer withthe information including the at least one network locator; such thatthe navigation service provides the network locator for the keywordservice to the client computer. The at least one keyword service servercomputer may receive the command data and a client computer identifierfrom the navigation service; and respond to the command data byresponding to the client computer with the information including the atleast one network locator. The command data may be derived from acommand string provided to the client computer, the command stringconsisting of a name portion and a keyword portion, where the nameportion includes the name and a name space identifier abutting the name,where the keyword portion includes the keyword. The keyword portion mayfurther include a keyword delimiter abutting the keyword, where thekeyword delimiter is selected from the group consisting of: #, !, “.”,$, and |, and where the name space identifier is selected from the groupconsisting of @, fb, in, and “.”. The other data may be provided to theclient computer through a user interface, where the command data isfurther derived from the other data. The at least one keyword serviceserver computer may receive the electronic authorization by receivingthe electronic authorization from the name owner or from the navigationservice. The at least one network locator may include a uniform resourcelocator (URL). The navigation service may not be a domain name system(DNS) service. The at least one keyword service server computer may befurther configured to solicit the name owner to provision at least onenetwork locator in association with the keyword and the entity name bysending an electronic message over a computer network to the name owner.The electronic message may include a recommended network locator. Thekeyword service may further be configured to receive, over a computernetwork, multiple electronic authorizations of respective name owners toprovision respective at least one network locators in association withthe keyword and respective entity names; and electronically store inkeyword service persistent memory respective at least one rulescorrelating at least the respective entity names to the respective atleast one network locators. The at least one rule may specify a databasequery. The at least one rule correlating at least the entity name andthe other data to the at least one network locator may correlate thekeyword, the entity name, and the other data to the at least one networklocator, where the command data further includes the keyword.

According to various embodiments, a system for provisioning a navigationservice is disclosed. The system includes: at least one navigationservice server computer communicatively coupled to a computer networkand configured to receive, over the computer network, an electronicauthorization to resolve command data including a keyword, an entityname associated with a name owner, and other data to at least onenetwork locator using a keyword service including at least one keywordservice server computer, such that the keyword service stores in keywordservice persistent memory at least one rule correlating at least theentity name and the other data to the at least one network locator; andan electronic memory configured to store a network locator for thekeyword service; where the at least one navigation service servercomputer is further configured to receive, over the computer network andfrom a client computer, command data including the entity name and theother data, and provide, over the computer network, a response to thecommand data, such that the client computer obtains the at least onenetwork locator.

Various optional features of the above embodiments include thefollowing. The client computer may obtain the at least one networklocator from the navigation service, where the at least one navigationservice server computer may be further configured to: provide, over acomputer network and to the keyword service, at least the entity nameand the other data, such that the keyword service correlates the entityname and the other data to the at least one network locator; and obtain,over a computer network and from the keyword service, the at least onenetwork locator; where the at least one navigation service servercomputer is further configured to provide, over the computer network,the response to the command data by providing the at least one networklocator to the client computer. The client computer may obtain the atleast one network locator from the keyword service, where the at leastone navigation service server computer may be further configured to:correlate the entity name and the keyword to the network locator for thekeyword service; where the at least one navigation service servercomputer is further configured to provide, over the computer network,the response to the command data by providing the network locator forthe keyword service to the client computer such that the client computerprovides at least the entity name and the other data to the keywordservice, such that the keyword service correlates the entity name andthe other data to the at least one network locator, such that the clientcomputer receives the at least one network locator from the keywordservice. The client may obtain the at least one network locator from thekeyword service, where the at least one navigation service servercomputer may be further configured to provide, over the computernetwork, the response to the command data by providing at least theentity name, the other data, and an identifier of the client computer tothe keyword service, such that the keyword service correlates at leastthe entity name and the other data to the at least one network locatorand provides the at least one network locator to the client computerusing the identifier of the client computer. The other data may includegeolocation data. The other data may include data identifying alanguage. The command data may be derived from a command string providedto the client computer, the command string consisting of a name portionand a keyword portion, where the name portion includes the name and aname space identifier abutting the name, and where the keyword portionincludes the keyword. The keyword portion may further include a keyworddelimiter abutting the keyword, where the keyword delimiter is selectedfrom the group consisting of: #, !, “.”, $, and |, and where the namespace identifier is selected from the group consisting of @, fb, in, and“.”. The other data may be provided to the client computer through auser interface, where the command data is further derived from the otherdata. The at least one navigation service server computer may be furtherconfigured to receive the electronic authorization by receiving theelectronic authorization from the name owner or from the keywordservice. The at least one network locator may include a uniform resourcelocator (URL). The navigation service may not be a domain name system(DNS) service. The at least one navigation service server computer maybe further configured to store at least one rule in navigation servicepersistent memory correlating an example keyword and the entity name toat least one example network locator. The at least one rule may specifya database query. The at least one rule correlating at least the entityname and the other data to the at least one network locator maycorrelate the keyword, the entity name, and the other data to the atleast one network locator, where the command data further includes thekeyword.

Note that, for any of the various method embodiments, computer readablemedia may be provided, where the computer readable media includeinstructions which, when executed by at least one electronic processor,cause the at least one electronic processor to perform the method.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated into and constitute apart of this specification, illustrate embodiments of the invention andtogether with the description, serve to explain the principles of theinvention. In the figures:

FIG. 1 is a diagram illustrating an exemplary keyword navigation system,consistent with certain disclosed embodiments;

FIG. 2 is a flow diagram illustrating exemplary processes performed by akeyword management server, consistent with certain disclosedembodiments;

FIG. 3 is an exemplary interface provided by a keyword resolution serverto enable a content provider to create, modify, and deletekeyword-webpage mappings, consistent with certain disclosed embodiments;

FIG. 4 is a flow diagram illustrating an exemplary method of resolving auser-supplied keyword to a content provider-specified webpage,consistent with certain disclosed embodiments;

FIG. 5 is a list of exemplary URLs containing URL keywords, consistentwith certain disclosed embodiments;

FIG. 6 is an exemplary HTTP request resulting from the entry of a URLcontaining a URL keyword, consistent with certain disclosed embodiments;

FIG. 7 is an exemplary HTTP response from keyword-enabled web server,consistent with certain disclosed embodiments;

FIG. 8 is an exemplary URL for requesting resolution of a URL keyword,consistent with certain disclosed embodiments;

FIG. 9 is an exemplary URL corresponding to a content provider-specifiedkeyword-webpage mapping, consistent with certain disclosed embodiments;

FIG. 10 is an exemplary implementation of an exemplary embodimentconsistent with the present invention;

FIG. 11 is an exemplary implementation of keyword/URL mapping on theserver side consistent with the present invention;

FIG. 12 is an exemplary implementation of keyword/URL mapping on theclient side consistent with the present invention;

FIG. 13 is an exemplary implementation of keyword/URL mapping using HTTPredirect;

FIG. 14 is flow diagram illustrating exemplary brand managementprocesses performed by a brand management component of the keywordmanagement server, consistent with certain disclosed embodiments;

FIG. 15 is an exemplary interface provided by a keyword resolutionserver to enable a content provider to manage brand-driven keywordmapping, consistent with certain disclosed embodiments;

FIG. 16 is an exemplary interface provided by a keyword resolutionserver to enable a third party to participate in brand-driven keywordmapping, consistent with certain disclosed embodiments;

FIG. 17 illustrates an example of a system and method for navigatingfrom an agent to a desired network resource, consistent with theprinciples of the invention;

FIG. 18 is a flowchart illustrating a method from the perspective of anavigation service according to various embodiments;

FIG. 19 is a flowchart illustrating a method from the perspective of anagent according to various embodiments;

FIG. 20 shows an exemplary computing system that may be used toimplement embodiments consistent with the invention; and

FIG. 21 illustrates an example technique for provisioning a navigationservice according to some embodiments.

DETAILED DESCRIPTION

This disclosure provides methods, systems, computer-readable media, andarticles of manufacturer for direct navigation from an agent to anetwork resource that is desired by a user. This disclosure furtherprovides methods, systems, computer-readable media, and articles ofmanufacturer that enable users of the agent to navigate to or connect toa desired network resource without necessarily knowing or having toenter the exact domain name, URI, URL, etc. corresponding to the desirednetwork resource.

Consider first the use-case example of a conventional internet user'sbehavior when looking for a desired network resource, such as a retailwebsite that sells a product, shoes. In this use-case example, the userdesires to purchase shoes from the website of a particular entityspecified by the user: a fictional retailer known as Gimbels. To dothis, the user typically first types into the navigation bar or omnibarof a browser a string of characters that generally describes what isdesired, such as “gimbels shoes” (without quotes) and presses enter. Thebrowser then typically sends this character string to a search enginethat returns many results, which are displayed by the browser. In thisconventional scenario, the retail brand and domain owner Gimbels has nocontrol over what the search engine displays to the user—in most cases,the search engine will display links to many network resources that areunrelated to Gimbels, such as links to competing retailers, off-pointproducts (e.g., sandals instead of shoes), irrelevant pages of Gimbels'website, or almost anything else that an advertiser may pay the searchengine to display. Similarly in this conventional scenario, the user maynot get the exact network resource the he specified and desires—aGimbels webpage that sells shoes—as the search engine will return linksto many different webpages unrelated to Gimbels often ahead of the linkto the Gimbels webpage.

Various embodiments consistent with the present invention allow anentity, such as a domain owner like Gimbels, to shape, specify, orotherwise guide the navigation results provided in response to generaldescriptions of desired network resources that can be associated with,related with, or otherwise mapped to one or more network resourcescontrolled or operated by the entity.

I. URL-Based Smart Navigation

FIG. 1 is a diagram illustrating an exemplary URL keyword resolutionsystem 100 that may be used to implement various disclosed embodiments,including exemplary system components. The components and arrangement,however, may be varied. URL keyword resolution server 120 may include aprocessor 122, a memory 123, input/output (I/O) devices (not shown), andstorage 121. URL keyword resolution server 120 may be implemented invarious ways. For example, URL keyword resolution server 120 may be ageneral purpose computer, a server, a mainframe computer, or anycombination of these components. URL keyword resolution server 120 maycommunicate over a link with network 115. For example, the link may be adirect communication link, a LAN, a WAN, or other suitable connection.Network 115 may include the internet. URL keyword resolution server 120may be standalone or it may be part of a subsystem, which may, in turn,be part of a larger system, such as a legacy domain registration system.

Processor 122 may include one or more known processing devices, such asa microprocessor from the Pentium™ or Xeon™ family manufactured byIntel™, the Turion™ family manufactured by AMD™, or any of variousprocessors manufactured by Sun Microsystems. Memory 123 may include oneor more storage devices configured to store information used byprocessor 122 to perform certain functions related to disclosedembodiments. Storage 121 may include a volatile or non-volatile,magnetic, semiconductor, tape, optical, removable, nonremovable, orother type of storage device or computer-readable medium.

In one embodiment, memory 123 may include one or more keyword resolutionprograms or subprograms 124 loaded from storage 121 or elsewhere that,when executed by URL keyword resolution server 120, perform variousprocedures, operations, or processes consistent with disclosedembodiments. For example, memory 123 may include a keyword registryprogram that authenticates a domain name and allows a domain namecontroller to set up and maintain keywords for the domain name; akeyword resolution program that receives user requests to resolve one ormore keywords within a domain, matches the keyword/domain namecombination to a target URL, and provides the target URL to the user; areporting program that displays statistics about keyword usage,resolution requests, and other metrics; an integrative support programthat links the other programs and allows them to use a common database,provides a common user interface, performs basic bookkeeping tasks,(such as storing the user's input, etc.), and provides user guidance andhelp; and a brand management program that allows a domain namecontroller to enable a third party to provide keywords for the domain.Memory 123 may also include other programs that perform other functionsand processes, such as programs that provide communication support,internet access, etc.

Methods, systems, and articles of manufacture consistent with disclosedembodiments are not limited to separate programs or computers configuredto perform dedicated tasks. For example, memory 123 may be configuredwith a keyword resolution program 124 that performs several functionswhen executed by processor 122. For example, memory 123 may include asingle program 124 that performs the functions of the keyword resolutionsystem, or program 124 could comprise multiple programs. Moreover,processor 122 may execute one or more programs located remotely from URLkeyword resolution server 120. For example, URL keyword resolutionserver 120 may access one or more remote programs that, when executed,perform functions related to disclosed embodiments.

Memory 123 may be also be configured with an operating system (notshown) that performs several functions well known in the art whenexecuted by URL keyword resolution server 120. By way of example, theoperating system may be Microsoft Windows™, Unix™, Linux™, Solaris™, anApple Computers operating system, Personal Digital Assistant operatingsystem such as Microsoft CE™, or some other operating system. The choiceof operating system, and even the use of an operating system, is notcritical to any embodiment.

URL keyword resolution server 120 may include one or more I/O devices(not shown) that allow data to be received and/or transmitted by URLkeyword resolution server 120. I/O devices may also include one or moredigital and/or analog communication input/output devices that allow URLkeyword resolution server 120 to communicate with other machines anddevices, such as web server 140 or client computer 150. URL keywordresolution server 120 may receive data from external machines anddevices and output data to external machines and devices via I/Odevices. The configuration and number of input and/or output devicesincorporated in I/O devices may vary as appropriate for certainembodiments.

URL keyword resolution server 120 may also be communicatively connectedto one or more data repositories 130, e.g., through network 115. Datarepository 130 may include one or more files or databases 131 that storeinformation and are accessed and/or managed through URL keywordresolution server 120. By way of example, the databases may be Oracle™databases, Sybase™ databases, or other relational databases, ornon-relational databases, such as HBase or Cassandra. The databases orother files may include, for example, data and information related todomain names, keywords for domain names, descriptions, statistics, andother data related to keywords, etc. Systems and methods of disclosedembodiments, however, are not limited to separate databases.

URL keyword resolution server 120 may also be communicatively connectedto one or more client computers 150 through network 115. Client computer150 may include a processor 151, a memory 152, and a web browser 153 tocommunicate with URL keyword resolution server 120 and/or web server140. Client computer 150 may also be communicatively connected to webserver 140 through network 115. In some embodiments, URL keywordresolution server 120 may send data to processor 151 and web browser153, and web browser 153 may display the data as a keyword registrationinterface. In some embodiments, a client computer 150 may communicatewith web server 140 using the HTTP protocol to retrieve and displaywebpages provided by web server 140. In some embodiments, a clientcomputer 150 may transmit URL and keyword data to URL keyword resolutionserver 120 and may receive back target URL data corresponding to a URLdesignated by a content provider for particular domain/keyword pairs.

Web server 140 may be owned or operated by a content provider or domainname controller and may store web pages and other internet resourcesassociated with one or more domain names. Web server 140 may include aprocessor 142, a storage 141, and a memory 143. Storage 141 may be avolatile or non-volatile, magnetic, semiconductor, tape, optical,removable, nonremovable, or other type of storage device orcomputer-readable medium and may contain data used to display individualweb pages. In disclosed embodiments, memory 143 may include one or moreweb server programs for receiving and responding to HTTP requests; oneor more server-side scripts 145 for providing dynamic webpages; and oneor more keyword resolution programs 146 for receiving and resolvingrequests for URL/keyword pairs. Each such program, for example, may beloaded from storage 141 or elsewhere.

FIG. 2 is flow diagram illustrating exemplary processes performed by akeyword management server, consistent with disclosed embodiments. Akeyword resolution service provider may provide the majority oftechnical infrastructure for enabling a content provider to implementURL keyword functionality consistent with the present invention. Forexample, the keyword resolution service provider may use a keywordmanagement server to provide content providers with an interface, suchas the interface depicted in FIG. 3, for registering and managing URLkeywords.

In step 205, after a user acting on behalf of a content provider logsinto the keyword management interface 300, the keyword management serverreceives a domain name (which may include path or query stringinformation as well) from the user indicating a domain name for whichthe user wishes to register a keyword. A domain name identifies a realmof authority or control of internet resources. Domain names are oftenhostnames that identify websites. For example, acmecorp.cc may be adomain name used by the Acme Corporation. Domain names are oftenregistered through domain name Registrars to signify an exclusive rightto use the internet resources associated with the domain names.

In step 210, for security purposes, the keyword management server mayfirst require the user to authenticate the entered domain name bydemonstrating that the user has authority to register keywords for it.For example, the keyword management server may create a meta tag for theuser to insert into the home page of the domain. Such a meta tag maylook like “<meta name=“keyword-verification”content=“djkaoieiosldisa”/>.” The keyword management server may storethe domain name and the value of the content field in a database orother file. After the meta tag has been inserted into the home page, theuser may return to the authentication process. The keyword managementserver may then examine the home page of the domain in order to detectthe presence of the meta tag. If the meta tag exists and has a contentvalue matching the value stored by the keyword management server, thenthe user may be verified as having control over the domain name.

In alternate embodiments, a user may be requested to set up a CNAMErecord in the domain name system (DNS). A DNS record stores informationused to resolve internet address requests into a physical resource. ACNAME record specifies that a domain name is an alias of another domain.The keyword management server may, for example, instruct the domain namecontroller to add a CNAME Host of “djkaoieiosldisa” and a CNAME Text of“www.resolvecom.com” to the DNS. The keyword management server may storethe CNAME Host with the domain name in a local database. After the CNAMErecord has been set up, the user may return to the authenticationprocess. The keyword management server may then query the DNS of thedomain to look for the CNAME Host and, if it is found and matches thestored CNAME Host, the user may be verified as the owner of the domainname.

For authenticated domain names, in Step 215, the keyword managementserver may allow a domain name controller to provide keywords for thedomain. The keyword management server may provide an interface, such asthe interface shown in FIG. 3, that allows a content provider or domainname controller to set up keywords. Keywords may be associated with adomain name, and the keyword management server may display the currentdomain name 305 in the interface. As shown in FIG. 3, the keywordmanagement server may receive at least keyword 310 and URL 315 from thedomain name controller, forming a keyword-URL pair. The URL identifies aspecific web page that the domain name controller desires to associatewith the keyword, such that a properly formatted to request to thedomain name 305 that also includes the keyword 310 will automaticallyredirect the user to URL 315.

URL 315 may be a web page hosted at domain 305, but it need not be. URL315 may be the address of any web page of any domain that the domainname controller chooses. After receiving the keyword and URL, thekeyword management server may store the keyword-URL pair in a databaseor other file. The keyword-URL pair is associated with the currentdomain name 305.

In addition to this information, the keyword management server may alsogather additional information, or metadata, related to a keywordthrough, for example, icon 320. This additional information may include,but is not limited to, a description of the URL or a description of thekeyword. A URL description may be a business description of the URL thatthe domain name controller chooses. The description may also be used onkeyword statistic reports and other reports generated by the keywordmanagement server.

The interface may also include a brand management component that allowsthe domain name controller to enable one or more third parties that donot own the domain to provide keywords for the domain. For example, theuser may press button 350 to request that the keyword management servergenerate a suggested list of third parties. The keyword managementserver may display this list to the domain name controller. The domainname controller may also provide suggested third parties to the keywordmanagement server that are not on the generated list. The brandmanagement component is further described in detail below.

A keyword-URL pair may also be mapped to a location. A location mayspecify a zip code, a state, an area code, a country, a geo-locationcode, or some other geographic identifier. For example, a domain namecontroller may desire to have a different web page display for websitevisitors located in Hawaii than for website visitors located inMinnesota. A keyword resolution server may receive a geo-location codefrom a device supporting GPS or may use a source IP address of thewebsite visitor to determine the location of the website visitor. Thekeyword resolution server may use this information to select akeyword-URL pair. The location allows a domain name controller to runregional advertising campaigns and direct website visitors to theappropriate regional offers.

A keyword may also have associated device metadata. The device mayrepresent, for example, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, etc. The device may enable the keywordresolution server to redirect a website visitor to the web pageappropriate for the device type. For example, a domain may have one webpage for mobile devices, such as a PDA or smart phone, and another webpage for all other devices. The keyword resolution server may beconfigured to determine the type of device that initiated the keywordresolution request for the provided domain/keyword and use the devicetype to choose an appropriate keyword-URL pair.

The keyword management server may use keyword type 325 of FIG. 3 toidentify keywords with locations or devices. For example, a keyword witha type of “R” may not have any associated locations or devices. Akeyword with a type of “L” may have locations associated with thekeyword and a keyword with a type of “D” may have devices associatedwith the keyword.

In step 220, after the content provider or domain name controller hasregistered, modified, or deleted keyword mapping as necessary, the usermay press button 330 to request that the keyword management servergenerate an appropriate client-executable program for embedding withincontent provider HTTP responses to enable user-provided URL keywords tobe detected and resolved, as further described below. And, in step 225the appropriate client-executable program, such as a JavaScript program,may be displayed for the user to copy and to place within the contentprovider's server logic.

FIG. 14 is flow diagram illustrating exemplary brand managementprocesses performed by a brand management component of the keywordmanagement server, consistent with disclosed embodiments. In step 1410,the keyword management server may receive brand management participationinformation indicating that a user acting on behalf of a contentprovider, such as a domain name controller, wants to participate inbrand management by enabling a third party to provide keywords for thedomain name. The user may submit the brand management participationinformation to the keyword management server by clicking on button 350of keyword management interface 300, or may use any other known methodto transmit the brand management participation information to thekeyword management server. Clicking on button 350 may redirect the userfrom keyword management interface 300 to a domain owner brand managementinterface. An exemplary domain owner brand management interface is shownin FIG. 15. While the domain owner brand management interface isseparate from the keyword management interface in this exemplaryembodiment, the brand management interface and the domain owner keywordmanagement interface may be combined into a single interface or may beseparated into more than two interfaces.

In step 1420, the keyword management server may generate a list ofsuggested third parties. The list may be generated automatically fromthe domain name registry or from third parties who have providedinformation to the keyword management server indicating that the thirdparties are interested in participating in brand management. The listmay be displayed to the user on the domain owner brand managementinterface, such as section 1510 of interface 1500 shown in FIG. 15. Thedomain name controller may review the list of available third partiesand select one or more of those third parties to enable the third partyto propose brand-driven keyword mapping for the domain. If the domainname controller wishes to enable a third party that wasn't displayed onsection 1510, the domain name controller may enter the name of thatthird party using one or more text boxes 1515. The domain namecontroller may submit the selection of the third party to the keywordmanagement server. For example, the domain name controller may submitthe selection to keyword management server by clicking submit button1514 on interface 1500.

In step 1430, the keyword management server may receive the domain namecontroller's selection of one or more third parties. The keywordmanagement server may receive the domain name controller's selection ofone or more third parties using any known method of receiving data.

In step 1440, the keyword management server may transmit third partyselection information to the third parties. The third party selectioninformation may include information relating to the domain name that hasauthorized the third party to submit proposed brand-driven keywordmappings. For example, the third party selection information may includethe domain name, the owner of the domain name, the type of site, and thedate and time of the third party authorization. The keyword managementserver may display the third party selection information on a thirdparty brand management interface, such as the exemplary third partybrand management interface shown in FIG. 16.

As shown in FIG. 16, the third party brand management interface mayinclude sections 1610, 1620, 1630, 1640, and 1650. They keywordmanagement server may display domain names that recently authorized thethird party to propose brand-driven keyword mappings in section 1610,and may display the names of one or more participants that have acceptedone or more of the third party's brand-driven keyword mappings insection 1620. The keyword management server may also display section1630, which allows a third party to enter a proposed keyword andproposed associated URL to submit to the user as a brand-driven keywordmapping by, for example, pushing submit button 1632. In the exampleshown in FIG. 16, third party “Alpha Corp.” is in the process ofsubmitting the keywords “Alpha,” “Alpha Widgets” and “Alpha Merger” andassociated URLs to the domain name controller for “Acmecorp.com.”

The keyword management server may display keywords approved by one ormore domain names in section 1640 and may display brand-driven keywordmappings that were rejected by one or more domain name controllers insection 1650. While not shown in FIG. 16, section 1650 may also includereasons why the domain name controller rejected the brand-driven keywordmapping. For example, the domain name controller may have rejected thebrand-driven keyword mapping because the keyword or the associated URLwas inappropriate. As another example, the domain name controller mayhave rejected the brand-driven keyword mapping with the keyword wasalready in use by the user or by another third party.

Returning to FIG. 14, in step 1450 the keyword management serverreceives the brand-driven keyword mapping from the third parties. Forexample, the third party may enter a keyword 1634 and an associated URL1636 (show in FIG. 16) and submit the brand-driven keyword mapping tothe keyword management server by pressing submit button 1632. If thethird party wishes to change the brand-driven keyword mapping, the thirdparty would submit the new mapping to the keyword management server forreapproval by the domain name owner. The domain name controller mayreview each revised keyword mapping, or may “opt out” of approval fortrusted third parties. Additionally, the domain name controller maydisable the third party from providing keyword mapping at any time.

In step 1460, the keyword management server may transmit thebrand-driven keyword mapping to the domain name controller. The keywordmanagement server may then display the brand-driven keyword mapping onthe domain owner brand management interface, such as on section 1520 ofbrand management interface 1500 in FIG. 15. The domain name controllermay then determine whether to accept or reject the brand-driven keywordmapping. For example, as shown in FIG. 15, the domain name controllermay select a button corresponding to “yes” if the domain name controlleraccepts the keyword mapping, or a button corresponding to “no” if thedomain name controller rejects the keyword mapping. Although not shownin FIG. 15, the domain name controller may also enter commentsindicating the reason why the domain name controller chooses to reject akeyword mapping or may also provide proposed alternate keywords orassociated URLs to the keyword management server or third party.Additionally, the domain name controller may auto-enable selection byrequesting that keyword management server compare the name of the thirdparty to the proposed keywords. If the third party name and the proposedkeyword are similar or identical, the domain name controller may directthe keyword management server to automatically accept the proposedkeyword mapping. Similarly, the domain name controller may direct thekeyword management server to automatically decline the proposed keywordmapping if the name of the third party and the keyword do not match, orif the keyword matches a list of prohibited keywords that is generatedby the keyword management server and/or by the domain name controller.

In step 1470, the keyword management server accepts or declines thebrand-driven keyword mapping based on the selection of the domain namecontroller. Once the keyword is accepted or declined, the keywordmanagement server notifies the third party. For example, the keywordmanagement server may display information relating to the approved orrejected brand-drive keyword mapping on third party brand managementinterface 1600, such as on sections 1640 or 1650.

In step 1480, the keyword management server stores the brand-drivenkeyword mappings accepted by the domain name controller in abrand-driven keyword registry database. The brand-driven keyword mappingis used to direct a client to a webpage in response to a user-suppliedURL keyword that is the same as or similar to the keyword in thebrand-driven keyword mapping. The brand-driven keyword registry databasemay also store additional information related to the brand-drivenkeyword mapping, such as the identity of the third party, whether thethird party has been given permission to automatically update thebrand-driven keyword mapping, statistical information, and various otherinformation associated with the brand-driven keyword mapping.

While FIG. 14 shows a process performed using particular steps,embodiments consistent with the invention need not perform all the stepsshown in FIG. 14, may perform additional steps, or may perform the stepsin a different order.

FIG. 4 is a flow diagram depicting an exemplary method of directing aclient to a webpage in response to a user-supplied URL keyword,consistent with certain disclosed embodiments. In the embodimentdepicted in FIG. 4, a client 410, such as an end user, may send an HTTPrequest to a content provider server 420 for a webpage associated with aURL (step 411).

For example, as depicted in FIG. 5, a user may type the URL 510“http://www.newnews.com/#earthquake” into the address bar of a browser,which may cause the browser to make an HTTP GET request 600, as depictedin FIG. 6, to a web server 420 that hosts the “www.newnews.com” domainname. Specifically, in response to the user specifying URL 510, the HTTPrequest 600 from the user's browser may request the resource 610, whichcorresponds to the root “/” directory from the web server 420 that hoststhe domain name 620 “www.newnews.com”. Typically, web servers will beconfigured by to transmit a default HTML file, such as “index.html”, inresponse to a request for the root directory.

URL 510 may comprise a resource string 510 a and a keyword 510 b, asindicated by the pound or hash symbol “#”. This technique of demarcatingURL keywords using hash symbols is similar, for purposes of syntax, tothe use of fragment identifiers in URLs, which are defined by theInternet Engineering Task Force's RFC 3986 URL specification.

In conventional use, a fragment identifier may be used to identify aspecific section within an HTML page received from a web server and toinstruct the browser to navigate directly to that section when renderingthe HTML page. For example, within the HTML text of a webpage, theauthor of the webpage may logically divide the content of the webpageinto an “introduction” section, an “analysis” section, and a“conclusion” section. The author may further place the HTML anchor tags‘<a href=“#introduction”>’, ‘<a href=“#analysis”>’, and ‘<ahref=“#conclusion”>’, before the content of the corresponding section.If a user requests a URL that includes the fragment identifier“#analysis” and there exists an HTML anchor tag for the “#analysis”fragment identifier, then the user's browser will not only download andrender the HTML of the retrieved HTML document, but will alsoautomatically scroll directly to the section of the HTML document thatis preceded by the “#analysis” fragment identifier. Thus, conventionallyfragment identifiers are processed entirely within the browser, asdepicted in FIG. 6, are not included in the specified resource 610 ofthe browser's HTTP request 600 to the web server, and are processedafter the content is retrieved via HTTP request 600. Furthermore, theconventional use of fragment identifiers does not generate additionalHTTP requests and is only used to decide what portion of the contentreturned is displayed to the user when rendering is performed in thebrowser.

As further described below, however, the syntax of the fragmentidentifier may be used instead to indicate a URL keyword in accordancewith the present invention. That is, the fragment identifier 510 b“#earthquake” may not indicate that the user is specifying to thebrowser an initial scrolling focus on a section of the webpage anchoredby the text “earthquake”, but rather that the user is requesting thatcontent provider server 420 respond by directing the user to whateverspecific webpage the content provider has designated for the keyword“earthquake”, which may be a webpage different from the webpage that wasinitially requested. In situations in which there is a conflict such aswhen the content provider is using the fragment identifier as both ananchor to an initial page and as a method to direct users to a specificwebpage, the content provider and/or the keyword resolution service maydetermine whether or not to make the anchor or the keyword dominant. Forexample, the keyword resolution service may automatically honor theanchor if there is no conflict with a keyword, and if there is aconflict, the keyword may take precedence. Thus, the client would bedirected to the specific webpage.

Continuing with this particular example, the user may have heard of arecent significant world event involving an earthquake in some foreigncountry. And, the user may further have desired to consult the websitewww.newnews.com for information about the event. However, rather thanfirst going to the newnews.com homepage and either searching forarticles discussing earthquakes, which might range from scientificexplanations of earthquakes to historical summaries of earthquakes, orattempting to navigate through traditional navigation techniques, suchas menus and sub-directories to find information on the recentearthquake (for which the user might not have enough information, suchas the relevant country, to even know where to begin looking), the usermay instead simply specify a base domain name 510 a and a keyword 510 bfor the topic sought in a URL.

By causing a browser to make an HTTP request to this base domainname/keyword combination, the user is essentially requesting that a webserver that hosts the www.newnews.com domain name provide the user withwhatever specific webpage that the NewNews content provider hasdesignated for that keyword. For example, once the NewNews contentprovider becomes aware of a major foreign earthquake, its editorialstaff may create a webpage that details all of the pertinent informationthat it believes users would seek if looking for a webpage that providesa basic overview of the recent earthquake news event. Once that webpageis created and assigned a URL, such as URL 315 of FIG. 3, editorial, orother non-technical, content providers may log into the keyword systeminterface 300 to register the new keyword “earthquake” for thewww.newnews.com domain name and to associate it with URL 315.

FIG. 5 depicts other potential forms of URLs in which keywords may beembedded consistent with embodiments of the present invention. Forexample, as in URL 520, which may be a preferred embodiment, a keyword(here, “anvil”) may be embedded in any form of URL for which a browsermay have sufficient information to make an HTTP request, and thereforethe scheme or mechanism (here, “http”) may not be present, and the rootdirectory “I” symbol may also be omitted between the domain name and thekeyword. In the example of URL 520, a user may append a keyword to thedomain name of an online retailer (here, “acmecorp.cc”) in order torequest a content provider-designated webpage for a particular type ofproduct for purchase (here, “anvil”).

As shown in URL 530, a keyword may comprise non-allowed URL characters,such as spaces, which may undergo URI encoding prior to transmission inan HTTP response in order to use separate, space-delimited words or toinclude special characters, such as non-ASCII characters. In the exampleof URL 530, a user may append a keyword to the domain name of a localbusiness (here “momandpopshop.com”) in order to request a contentprovider-designated webpage for information about a particular promotionor event (here, “green light special”) that is occurring at the localbusiness.

As shown in URL 540, a keyword may also include wildcard, regularexpression, or other characters to allow for flexible string matching ofkeywords; or may include alternative keywords, for example, in whichalternatives are separated by a pipe “|” character. URL 540 alsodemonstrates that a keyword need not follow a domain name directly, butmay instead be placed within a directory structure or other path withinthe URL. A keyword placed within a path may be handled in a variety ofways. For example, the keyword may be given preference over any pathinformation such that any path in the URL is simply ignored if a keywordis found.

Alternatively, any path that precedes a keyword may limit the scope orotherwise provide a relevant name space for that keyword. For example, acontent provider may designate a first webpage for the keyword“admission” if it is placed within the “/students/undergraduate/” pathin a URL (e.g., providing admissions information for undergraduatestudents) and a second webpage for the keyword “admission” if it isplaced within the “/students/graduate/” path in a URL (e.g., providingadmission information for graduate students). Similar techniques may beemployed for content providers that offer “vanity” URLs within a singledomain name to various different companies or organizations. Forexample, in the case of Facebook.com, which offers vanity URLs, such as“www.facebook.com/cocacola” or “www.facebook.com/toyota”, the samekeyword (e.g., “#2011challenge”) may be linked to different webpagesdepending on whether it occurs within the “/cocacola” path or the“/toyota” path.

In the example of URL 540, a user may append a keyword to the domainname of a university (here, “www.vanderbilt.edu”) or other non-profitorganization (and further within a path following the domain name) torequest a content provider-designated webpage for general information(e.g., a table of contents) about a particular subject (here,“admissions”).

As shown in URL 550, a keyword may also be embedded within or appendedto a query string within a URL. Similar to URL 540, the query stringwithin URL 550 may be either ignored once a keyword is detected or mayprovide a name space within which the keyword has a separate or distinctmeaning. In some embodiments, a URL query string may simply provideadditional parameters to be applied to any webpage returned in responseto a user-specified keyword, such as an instruction that such a webpageshould be provided in a particular language (here, “fr” for French) orin a particular format (here, formatted for a display on a mobiledevice). In the example of URL 550, a user may append a keyword to thedomain name of an online information service provider (here,“site.netops.globalsecuritiestrade.org”) to request a contentprovider-designated webpage that provides status or real-timeinformation about a particular topic (here, “ETFs”).

As shown in URL 550, a keyword may be appended to a domain name thatincludes multiple sub-domain names. And, similar to the path of URL 540,the specificity of the preceding domain name may define a name spacewithin which the keyword has a separate or distinct meaning. Forexample, a content provider may designate a first webpage for thekeyword “ETFs” if it follows the more generic second-level domain name“globalsecuritiestrade.org” (e.g., providing information about ETFproducts in general) and a second webpage for the keyword “ETFs” if itfollows the more specific sub-domain “netops.globalsecuritiestrade.org”or any other sub-domain within that sub-domain (e.g., providingreal-time trading prices for various exchange traded funds). While FIG.5 shows URLs including top-level domains, second-level domains,third-level domains, and fourth-level domains with the fragmentidentifier and keyword following the top-level domain, embodimentsconsistent with the present invention may implement the fragmentidentifier and keyword at any domain level within the URL and/orimplement the fragment identifier in URLs including one or more of anydomain level.

And, as shown in URL 560, multiple keywords 560 a, 560 b, and 560 c maybe placed in a URL. In the example of URL 560, a user may appendmultiple keywords to the domain name of an online retailer to requestone or more content provider-designated webpages for particular productnames. Various techniques could be employed for processing multiplekeywords, including processing each keyword to determine whether a matchexists and providing a webpage in response to the first keyword that hasa designated webpage; assigning priority orderings for various keywordsand providing the webpage designated for the highest ranked keyword inthe URL; or providing specific webpage mappings for distinct keywordcombinations (e.g., a first webpage for keyword 560 a, a second webpagefor keyword 560 b, a third webpage for keyword 560 c, and a fourthwebpage for the combination of keywords 560 a, 560 b, and 560 c).

Other techniques or syntax may be used to identify URL keywords. Forexample, a URL keyword may alternatively be identified by one or morecharacters, such as “$”, “|”, or “@”, that are not valid URL charactersunless converted to hexadecimal format. However, since such charactersmay also be used to define file names or valid paths within a URL, insome embodiments it may be preferable to use the hash symbol instead,since most web browsers are configured to omit any fragment identifiers(identified by the hash symbol) from an HTTP request, and thus there maybe no danger that a web server that did not provide functionality fordomain-specific keywords would attempt to locate a file that actuallycontained the keyword text in its file name.

A URL keyword of the present invention may also include international orspecial characters that are otherwise disallowed for URLs, since anysuch characters may simply be converted to hexadecimal form by theuser's browser prior to transmission in an HTTP request. For example, acontent provider, such as a bookseller that desires to create a keywordwebpage for books directed to résumé drafting may create a keyword thatuses the appropriate international characters, knowing that users maysimilarly specify the keyword “#résumé”, which may be subjected to URIencoding to become “#r%C3%A9sum%C3%A9” by users' browsers when HTTPrequests are made.

Returning to FIG. 4, in step 421, content provider server 420 receivesHTTP request 610 and responds by transmitting an HTTP response 700, asdepicted in FIG. 7. HTTP response 700 includes both header information710 and payload data 720. Because keyword 510 b may not be included inHTTP request 600 to content provider server 420 (since, when formattedas a fragment identifier, it may be omitted by the client's browser), atthis point, content provider server 420 may not know whether the requestfor “www.newnews.com/” is meant as an actual request for a the rootwebpage at www.newnews.com or was merely used to specify the domain namefor a domain-specific keyword. Therefore, content provider server 420may transmit a payload 720 that includes the HTML text for the“index.html” file on the server.

However, in order to allow for the possibility that client 410 may berequesting a domain-specific keyword, content provider server 420 mayalso include a small amount of client-executable code within the HTMLdocument/payload 720, such as, for example, “<head>” section 721. Whilein this exemplary embodiment the client-executable code is includedwithin the “<head>” section, the client-executable code may be includedanywhere in the HTML document. The client-executable code may comprise aJavaScript® or other client-executable program 721 b the contents ofwhich are provided directly by content provider server 420.Alternatively, content provider server 420 may include only a link 721 ato a program file that resides on another server, such as keywordresolution server 430. Using this approach, client 410 may make aseparate HTTP request to keyword resolution server 430 for the programfile specified by link 721 a, and, once the program file is received,may execute the program file within the client's browser program.

In step 412, client 410 may execute the client-executable program, forexample, under a browser rule that any scripts contained within the“<head>” section 721 are to be executed prior to parsing or renderingany content in the “<body>” 722 section of the HTML document 720. Theclient-executable program may identify any URL keywords that the userincluded in the requested URL. For example, if keywords are formatted asfragment identifiers, because the client-executable program is executedwithin client 410, as opposed to on the content provider server 420, theclient-executable program may have access to such fragment identifiers.In the example of URL 510, the client-executable program would identifythe “#earthquake” fragment identifier as a domain-specific keyword.

In step 412, in response to identifying the presence of one or moredomain-specific keywords, the client-executable program may cause client410 to make a separate HTTP request to a separate keyword resolutionserver 430 to request the URL for the specific contentprovider-designated webpage for the keyword or keywords. For example, asdepicted in FIG. 8, in the case of URL 510, client 410 may make an HTTPGET request to keyword resolution server 430 using URL 800. URL 800 mayinclude the domain name 810 of the keyword resolution server; the path820 of a server-side script on keyword resolution server 430 capable ofperforming keyword-lookup operations; and a query string 830 thatspecifies both the original URL 830 a and the domain-specific keyword830 b requested by client 410.

For example, the client-executable program may make a synchronous or anasynchronous HTTP request to the keyword resolution server 430 usingAsynchronous JavaScript and XML (“AJAX”) or JQuery techniques known bythose skilled in the art. The client-executable program may also make anHTTP request to the keyword resolution server using an HTML “<IFrame>”element or an HTML “<script>” element that has a target pointing to aURL hosted by the resolution server. Those skilled in the art willappreciate other means for providing the user-requested URL anddomain-specific keyword to keyword resolution server 430 for resolution.

In 431, keyword resolution server 430 may determine which specificwebpage, if any, on the content provider's website has been designatedto be served for the requested keyword, and provide the target URLcorresponding to that specific webpage back to the client. For example,in the case of URL 510, keyword resolution server 430 may provide client410 with the URL 900, as depicted in FIG. 9, which is the same URL thatthe content provider had specified as URL 315 in the keywordspecification interface 300. Keyword resolution server 430 may provideURL 900 to client 410 as a simple text string in an AJAX response.Alternatively, keyword resolution server 430 may redirect client 410 toURL 900, for example using an HTTP 301 or 302 Redirect.

In step 413, client 410 may make a new HTTP request to content providerserver 420 for the target URL provided by the keyword resolution server.For example, client 410 may make an HTTP request to content providerserver 420 for the webpage associated with URL 900. And, in response,content provider server 420 may provide an HTTP response that includesthe HTML text for the webpage specified by URL 900, thus providingclient 410 with the webpage that the content provider has designated forthe keyword “earthquake.” The client may then render and display thewebpage specified by URL 900 in the main browser window for the user tosee and interact with.

The foregoing technique for providing content provider-designatedwebpages in response to user-specified keywords presents severaladditional benefits that merit brief treatment here. Clients may useexisting browser programs request domain-specific keyword webpageswithout any need to modify or enhance the functionality of the browserprograms, such as by browser plugin or add-on. Rather, to practice thepresent invention, browsers need only provide users with the ability toinclude fragment identifiers in URLs and include basic functionality forexecuting client-executable programs such as JavaScript®.

Content providers may likewise implement domain-specific keywordfunctionality in response to HTTP requests with only trivialmodifications to existing server-side scripts or programs. Specifically,a content provider need only include a small amount of client-executablecode within each webpage in a domain for which the content providerwishes to provide domain-specific keyword functionality. The contentprovider may then leave it to the client's browser and the relevantkeyword resolution server to perform the actual keyword resolutionoperations. In fact, provided the content provider includes therequisite client-executable program in HTTP responses for webpages, thecontent provider's servers may remain completely agnostic as to whethera client has either requested a domain-specific keyword or is making arequest for a specific webpage in response to a previous keywordresolution. Because the content provider server always returns anyrequested webpages along with the client-executable keyword resolutionprogram, the content provider can ensure that clients that requestedwebpages in order to actually render them receive such webpages, whereasclients that request webpages merely as a means of specifying a domainname space for a particular URL keyword are provided with theclient-executable program necessary to resolve the keyword.

Similarly, by using the syntax of fragment identifiers to specifydomain-specific keywords, users can make HTTP requests that include URLkeywords to any content provider, whether or not that content provideris keyword-capable, without any danger of generating server responseerrors. Because browsers do not transmit fragment identifier text to webservers, the inclusion of a domain-specific URL keyword in an HTTPrequest to a web server that is not keyword-capable should not generateany errors, but should instead simply result in the webpage of the URL,without the fragment identifier, being downloaded and displayed. And,even for web servers that are keyword-capable, if the user specifies adomain-specific keyword for which the content provider has notdesignated a webpage, the keyword resolution server may simply providean empty string in response to a resolution query, once again resultingin the webpage of the base URL being downloaded and displayed.

In the case where a keyword is found to correspond to a contentprovider-designated webpage, because the executable code for requestinga resolution of the keyword and redirecting the client to the resolvedtarget URL is within the “<head>” section of the original HTML documentreturned by the content provider server, such code may be executedbefore any rendering of the original HTML document takes place. Thus,user should never see the originally requested HTML document displayed,even if only briefly, but it should appear to the user as though he orshe went straight to the webpage associated with keyword.

Also, the use of a separate keyword resolution server, along with akeyword management interface 300, allows non-technical employees of acontent provider to create, modify, or delete keyword-webpage mappingsas business needs dictate without the need to involve technicalemployees such as IT personnel. Indeed, since the content provideritself can maintain the keywords without the need for any specific ITskills, costs can be reduced. Furthermore, content changes quickly andexisting traditional navigation techniques would require an ITprofessional to reconfigure the web server.

In another embodiment, a content provider itself may perform the role ofkeyword resolution service provider. In particular, theclient-executable program provided by the content provider server to theclient may instruct the client, after identifying one or more URLkeywords, to query the content provider itself, rather than a separatekeyword resolution server, for the content provider-designated webpagescorresponding to the identified keywords.

The present invention is not limited to circumstances in which a usermanually types a domain-specific keyword into a URL. Rather, thedomain-specific keyword may be included in a requested URL in anymanner, such as being specified within a hyperlink in an existing HTMLdocument, being included in navigation “bookmark”, being provided by aweb server, such as in the form of an HTTP Redirect, or being includedwithin a native mobile phone application.

The present invention may also allow users to use wildcards or regularexpressions in keywords, such as “engineer*”, which may resolve to“engineer,” “engineers,” “engineering,” “engineering schools,” etc. Insome embodiments, if there are a sufficient number of potentialresolutions for a wildcard or regular expression keyword, the user maybe prompted with a list of choices.

Those skilled in the art will also appreciate that although both theoriginally requested base URL of step 411 and target URL of step 413 maybe hosted by the same content provider entity, the resources hosted bythe respective URLs may be hosted by separate web servers. Also,although described predominantly in this application as“domain-specific” keywords, those skilled in the art that the conceptmay be expanded to provider-specific keywords. For example, a singlecontent provider may own and host the distinct domain names“zulumail.tv” and “zmail.tv”, both of which are directed to the samehosting service or are hosted by the same web servers. And, the contentprovider may designate a single webpage for the keyword “#forwarding”,regardless of whether it is requested by a user as part of a URL basedon either domain. That is, both “http://zulumail.tv/#forwarding” and“http://zmail.tv/#forwarding” might resolve to the URL“http://zmail.tv/user_options/mail_handling/automatic_forwarding.htm”.

Similarly, the concept may be expanded to allow a first content providerto designate another content provider's webpage for a given keyword. Forexample, if a number of smaller weather-related websites rely on alarger service provider to supply real-time weather information, thecontent provider responsible for each smaller website may designate awebpage hosted by the larger service provider for the keyword “#storms”.

In other words, a content provider is not limited in any way to thespecific webpage that it may designate for a given keyword. However, asdescribed with respect to FIG. 2, a content provider may be limited inthat it may not designate keywords for websites or domains that it doesnot either own or control or have authority over. And moreover, a givencontent provider-designated keyword may have a meaning only within aspecific domain name, which also may include a URL path, a query string,and/or a port number.

Furthermore, there are a number of implementation options forembodiments of keyword/URL mappings. As shown in FIG. 10, in the genericcase, a user 1010 may input a direct navigation URL, such as“example.com#keyword,” into a browser 1020, causing the browser 1020 tomake an HTTP GET request to the example.com server 1030. In response tothe user specifying the direct navigation URL, the GET request from thebrowser 1020 may request the resource that corresponds to the root “/”directory from the server 1030 that hosts the domain name “example.com.”Generally, web servers transmit a default HTML file, such as“index.html,” in response to a request for the root directory, alongwith the requisite keyword/URL mapping and keyword resolution program,such as, for example, a JavaScript code. Browser 1020 may then implementthe keyword resolution program to determine the URL to keyword mappingand the mapped URL. The Browser 1020 may then transmit a request to theserver 1030 for the mapped URL page, and in response to the request, theserver may return the target page (i.e., the page associated with thekeyword). Alternatively, the content provider server could requestresolution, or instruct the client to request resolution, of the keywordfrom a separate server, such as a keyword resolution server.

The keyword/URL mapping can be performed in a number of ways. Forexample, the keyword/URL mapping can be performed on the server side, becloud-based, or performed on the client side. FIG. 11 is an exemplaryimplementation of keyword/URL mapping performed on the server side. Asshown in FIG. 11, there may be an internet user 1110, a browser 1020, aserver 1130, and a keyword registry 1140. The keyword registry 1140 maybe configured by a domain owner 1150 in a way that the domain owner 1150associates the keyword to a particular website in the domain, and may bea separate server or may be part of server 1130 itself. Additionally, abrand-driven keyword registry (not shown) may be separately provided, ormay be combined keyword registry 1140.

As shown in FIG. 11, user 1110 may input a direct navigation URL, suchas “example.com#keyword” into browser 1120. The browser 1120 maytranslate the “#” to some other character, such as “@” and make arequest to the server side using the keyword and the new character.Server 1130 may then communicate with keyword registry 1140 to determinethe URL mapped to the keyword, and the server 1130 may transmit adefault HTML file, such as “index.html,” in response to the requestalong with a keyword resolution program, such as, for example, aJavaScript code. Browser 1020 may then transmit a request to the server1130 for the mapped URL page, and in response to the request, the servermay return the target page.

FIG. 12 is an exemplary implementation of keyword/URL mapping performedon the client side. As shown in FIG. 12, a user 1210 may input a directnavigation URL, such as “example.com#keyword” into browser 1220, causingthe browser 1220 to make an HTTP GET request to the example.com server1230. In response to the user specifying the direct navigation URL, theGET request from the browser 1220 may request the resource thatcorresponds to the root “/” directory from the server 1230 that hoststhe domain name “example.com.” Generally, web servers transmit a defaultHTML file, such as “index.html,” in response to a request for the rootdirectory, along with the requisite keyword/URL mapping and keywordresolution program, such as, for example, a JavaScript code. Browser1220 may then implement the keyword resolution program to communicatewith a cloud infrastructure 1240 that may include a keyword registry1242. The cloud infrastructure 1240 will determine the URL to keywordmapping and the mapped URL, and will transmit the mapped URL to browser1220. The browser 1220 may then transmit a request to the server 1230for the mapped URL page, and in response to the request, the server mayreturn the target page.

Keyword/URL mapping may also be performed entirely on the client side.In some embodiments, a client may maintain a local file system ordatabase for the resolution of URL keywords, rather than relying oneither the content provider or a third-party resolution service providerto resolve keyword/URL mappings. For example, HTML 5 allows forclient-executable code, such as JavaScript®, to access or query a localdatabase in order to retrieve data or content. The client-executableprogram received from the content provider may rely on such a localdatabase to look up the mapping between a keyword and URL, and, once therelevant URL is located, may direct the browser directly to the URL,thus cutting out at least one HTTP request from the client to a remoteserver from the process. In other embodiments, the client-executablecode can itself generate the local file system or database for theresolution of URL keywords.

In another embodiment, URL keyword resolution operations may beperformed entirely on the server side without relying on the client toexecute any client-executable code. For example, as shown in FIG. 13, auser 1310 may input a direct navigation URL, such as“example.com#keyword,” into browser 1320. If the URL keyword isdelimited by a character other than a hash symbol (e.g., a “@”character), then, unlike the fragment identifier, the keyword may betransmitted to the content provider server 1330 as part of the client's1320 initial HTTP request. The content provider server 1330, forexample, may identify the keyword, determine the appropriate URL mappingfor the keyword, and redirect the client 1320 (e.g., using an HTTP 301Redirect instruction) to the appropriate URL for the keyword, allwithout relying on the client 1320 to execute any client-executablecode. Alternatively, the content provider server could requestresolution, or instruct the client to request resolution, of the keywordfrom a separate server, such as a keyword resolution server.

In another embodiment, if a client requests a keyword that has not beencreated or designated by a content provider, the client-executableprogram, keyword resolution server, or content provider server mayprovide for certain default options. For example, in response to arequest for a non-existent keyword, the client may simply render thewebpage identified by the base URL of the initial HTTP request.Alternatively, the client may be provided with a webpage, JavaScriptalert, or other notification that the user has requested a non-existentkeyword. The user may also be provided with a list of potentiallysimilar existing keywords that the user may select in lieu of thenon-existent, originally requested keyword. The user may also beprovided with a traditional list of webpages generated using traditionalkeyword searching techniques. The user may also be prompted with a listof potential matching keywords from which the user may select.

In yet another embodiment, if a user inputs the hash tag to request akeyword the content provider, a hash module may provide a list of all ofthe available keywords associated with a particular domain. For example,the hash module may be a browser add-on or plugin that determines inreal-time whether or not a user has entered a hash tag into the addressbar of a browser. If so, the auto completion module will communicatewith one or more of the content provider, client-executable program,keyword resolution server, or content provider server to determinewhether any keywords associated with that particular domain. The morealphanumeric characters entered by the user into the browser, thenarrower the list of available keywords associated with the particulardomain. If there are keywords associated with the domain, the hashmodule may generate a pop-up list including those key words. If therearen't keywords associated with the domain, the hash module may redirectthe user to a search service page. According to some embodiments, thehash module may direct the user to a search page for the web site of theprovided URL.

In another embodiment, a smart navigation module may be provided toinform a user if a particular domain has keyword smart navigation. Forexample, the smart navigation module may be a browser add-on or pluginthat reviews, in real-time, a domain input into an address anddetermines whether or not that particular domain has associated keywordsby communicating with one or more of the content provider,client-executable program, keyword resolution server, or contentprovider server. If so, the smart navigation module may provide anindication that the domain has associated keywords such as, for example,changing the color of the address bar or inserting a particular graphicinto the browser or associated webpage.

The resolution service provider, in addition to providing a keywordmanagement interface and/or keyword resolution service, may also providecontent providers with access to rich metrics and statistics concerningkeyword resolution requests from clients. For example, the interface 300of FIG. 3 may also allow a user and/or content provider to view and/ordownload the number of times that each created keyword has beenrequested from clients. As another example, the resolution serviceprovider could track how many times keywords have been used, who usedthe keywords, the type of keyword used, the websites visited, andvarious other information using, for example, cookies. Interface 300 mayalso provide information about the number of requests for variousnon-existent keywords by users, thus allowing the content provider todetermine the need for creating additional keywords as a result of userdemand. Such non-existent keyword information may also compriseinformation about misspellings of existent keywords to inform thecontent provider of the need to create additional keywords to accountfor misspellings or homophones of existing keywords or to improve uponpermissible wildcard or regular expression matching functionality.Similar information may be provided to third parties in the brand-drivenapproach.

The resolution service provider may also provide malware-free securenavigation. Since the number of websites available on the internet is solarge, it's practically impossible to scan all of them for malware.However, since the resolution service provider knows the URL associatedwith a particular keyword, the resolution service provider could scanthe URL to determine whether its free of malware using, for example, thesystems and methods for malware detection and scanning disclosed in U.S.patent application Ser. Nos. 12/982,508 and 12/982,540, the entirecontents of which are incorporated herein by reference in theirentireties. Accordingly, when a user enters a direct navigation URL suchas “example.com#keyword” into a browser, the user has a high levelguarantee that the URL is safe for browsing and doesn't includemalicious content.

In another embodiment, one or more of the content provider, theclient-executable program, keyword resolution server, or contentprovider server may automatically optimize a particular website based onan identification of the client device. For example, theclient-executable program may identify the user's device (e.g., a mobilephone) to forward the user to the particular device's version of thewebsite. The client executable program may automatically optimize thewebsite using, for example, the method discussed in U.S. patentapplication Ser. No. 13/078,680 filed on Apr. 1, 2011 entitled “Systems,Apparatus, and Methods for Mobile Device Detection”, which is herebyincorporated by reference in its entirety.

II. Name-Space-Based Smart Navigation

Various embodiments consistent with the present invention utilize namesfrom general name spaces, including non-DNS (e.g., non-URL) name spaces.That is, disclosed embodiments can work with any name space (and evenmore than one name space at a time). In general, a name space includesnames, and a name owner has authority for a name space (or subspace),where that authority can in some cases be delegated. Name spaces can bepublic or private, hierarchal or flat. Specific, non-limiting examplesof name spaces follow.

The collection of all top-level domain names forms a name space.Further, certain sub-collections of all domain names form name spaces,such as the collection of all second-level domains of a top-leveldomain, third-level domains, all subdomains, etc. The term “domain” in“domain name” refers to the fact that each name has an “owner” that isauthoritative for a “space” associated with the name. In traditionalDNS, which has a hierarchical structure, the name owner is authoritativefor any subdomains under the domain, e.g., the owner of “example.com” isauthoritative for “a.example.com”, “b.example.com,” etc. The name ownermay delegate authority for those subdomains to another party, but it isthe name owner's authority over its “domain” that is delegated.

Many non-DNS name spaces exist. For example, the TWITTER™ name space isa non-DNS, flat, public name space. TWITTER is a microblogging servicethrough which users can share short messages with their followers. EachTWITTER account has a unique name or “handle,” a string beginning withthe “@” character, such as “@example_brand”.

Other example name spaces include the FACEBOOK™ name space and theLINKEDIN™ name space. Regarding these resources, in general, a user cannavigate to an example user's page by entering a URL of the form,respectively, http://www.facebook.com/example_user_name orhttp://www.linkedin.com/example_user_name. The form of these URLsprovides name spaces consisting of all names of the formexample_user_name for which an account exists in the respectiveresource.

Another name space is the space of email addresses. Embodimentsdisclosed herein can allow a general user look up information such as anexample user's personal home page by email address, using a commandstring in a form such as “user@example.com!home”, wherein“user@example.com” is an email address.

Yet another example is the name space defined by shortened URLs.Shortened URLs have been adopted as abbreviated versions of potentiallylong and complex URLs. They typically have the form “name/code” where“name” is a short domain name and “code” is a short string identifying aparticular reference to the full URL. An entry of the form“bitly:name/code!keyword” may be processed by a navigation serviceaccording to embodiments disclosed herein as a way to lookup additionalinformation about a shortened URL or the resource it refers to.

Examples of private name spaces include lists of users within a company,and lists of resources and/or devices within a local-area network, suchas in a user's home.

For clarity of explanation, various embodiments are described herein inthe context of a use case where the owner of a brand (e.g., Gimbels)also is the registrant for a domain corresponding to that brand (e.g.,“.gimbels”). The invention, however, is not solely limited to thiscontext and has applications far outside of this context.

FIG. 17 illustrates an example of a system 1700 for navigating by anagent 1710 to a desired network resource, consistent with the principlesof the invention. Complementary methods are described along with thedescription of FIG. 17. As shown, system 1700 includes a user 1705,which communicates with an agent 1710, which communicates with anavigation service 1780.

In various embodiments, the user 1705 may be anything that can provideinput navigation data 1751 characterizing, regarding, specifying orotherwise describing a desired network resource and that can provideinput data 1726 specifying or selecting at least one presentedsuggestion 1714 (described further below). The user can specify thenavigation data 1751 by, for example, typing it into an appropriatefield, clicking on a link that has a compatible syntax, or speaking intoa microphone that can capture sounds reflecting such data. One exampleof input navigation data 1751 may be the string of characters “gimbelsshoes”. In some embodiments, the user 1705 may be a human user or acomputing system programmed to perform the functions of providing inputnavigation data 1751 and input data 1726.

Thus, a user 1705 can be a computer or executing computer code. Such auser can provide any, or a combination, of input navigation data 1751,selection choice data 1771, and input data 1726. For example, executingcomputer code (e.g., an application) can navigate to content associatedwith one or more defined keywords in an automated way by providingnavigation data 1751 to a navigation service 1780 in an automatedmanner. Such executing computer code does not require human interactionat the time that it provides navigation data to the navigation service.

In various embodiments, the agent 1710 (also referred to as a“navigation client,” which is one example of an agent 1710) may beanything that can interact with the user 1705 and with the navigationsystem 1780 as described herein. In some embodiments, the agent 1710 mayalso connect to and interact with network resources specified by networklocation data 1772 or by network locators 1735-1737. The agent 1710generally accepts, receives, obtains or otherwise accesses input datafrom the user 1705 and accepts, receives, obtains or otherwise accessessuggestion data 1762 and network location data 1772 from the navigationservice 1780. A user 1705 may input characters into an agent 1710 by,for example, typing such characters into a field, clicking on a linkthat provides such characters, or providing audio input. Regarding audioinput, raw audio data can be converted using known techniques intocharacter strings usable by embodiments by any of a variety ofinstrumentalities, such as agent 1710, navigation service 1780, or aseparate computer communicatively coupled to agent 1710 and/ornavigation service 1780. Further regarding audio input, a trigger workcan be employed such that when the user 1705 utters he trigger word, anaudio interface activates. The trigger word can be, for example, “at” oranother name space prefix. The agent 1710 also generally outputs,transmits, opens or otherwise provides access related to suggestion data1762 and network location data 1772 for the user 1705 and generallyoutputs, transmits, opens or otherwise provides access related tonavigation data 1751 and suggestion choice data 1771 for the navigationservice 1780. Various embodiments of the agent 1710 may perform otherfunctions as well. In various embodiments, the agent 1710 may beimplemented in software, firmware, hardware, or any combination thereof.In some exemplary embodiments, the agent 1710 may be a browser, astandalone application, a plugin or add-on to another program (e.g., abrowser plugin), or a service, (e.g., a web service), among otherthings. The agent can be present in a navigation application (e.g., abrowser) in a mobile device such as a smart phone. The agent 1710 may beseparate from a web browser, an interface or control within a webbrowser, or even a modification of a web browser's address bar. In someembodiments, the agent 1710 can be implemented on a client computer orin web browser as disclosed in Section I, above. More particularly, theagent 1710 can include some or all features, functions, communications,implementation details, code, algorithms, architecture, structure, andproperties of the web browser disclosed in Section I, above.

In various embodiments, the navigation service 1780 may be anything thatcan interact with the agent 1710 and the user 1705 as described herein.The navigation service 1780 generally accepts, receives, obtains orotherwise accesses input data from the user 1705 and accepts, receives,obtains or otherwise accesses navigation data 1751 and suggestion choicedata 1771 from the agent 1710. The navigation service 1780 alsogenerally outputs, transmits, opens or otherwise provides access relatedto suggestion data 1762 and network location data 1772 for the agent1710. In various embodiments, the navigation service 1780 may beimplemented in software, firmware, hardware, or any combination thereof.In some exemplary embodiments, the navigation service 1780 may be astandalone application, a server application, a plugin or add-on toanother program (e.g., a browser plugin), or a service, (e.g., a webservice), among other things. In some embodiments, the navigationservice 1780 and the agent 1710 may be implemented on separate computingsystems and may communicate via a network(s) (not shown), such as theinternet or a combination of the internet and a cellular telephonenetwork. In other embodiments, the navigation service 1780 and the agent1710 may be implemented on the same computing system, either as separateprograms or in the same program. In some embodiments, the navigationservice 1780 can be implemented in or as a URL keyword resolution serverdescribed in Section I, above. More particularly, the navigation service1780 can include some or all features, functions, communications,implementation details, code, algorithms, architecture, structure, andproperties of the URL keyword resolution server disclosed in Section I.

As shown in the example of FIG. 17, system 1700 also includes entityrepresentations 1720, which are consulted, accessed, and otherwiseutilized by the navigation service 1780 and the agent 1710. In someembodiments, the entity representations 1720 can be implemented asstored keyword mappings and/or the contents of a keyword registrydatabase as disclosed in Section I, above. More particularly, the entityrepresentations 1720 can include some or all features, functions,communications, implementation details, code, algorithms, architecture,structure, and properties of the stored keyword mappings and/or contentsof the keyword registry database disclosed in Section I.

In various embodiments, an entity is something that controls, or has theright to control, or has some other interest in, a network resource(s),including, for example, a domain or name space. From the use-caseexample above, Gimbels is an entity because it owns the (perhapstrademarked) brand “Gimbels” and because it is the registrant for thedomain “.gimbels” and so has the right to control domains ending in“.gimbels” which specify network resources, such as Gimbels web pages.An entity can be a content provider and/or domain name controller asdescribed in Section I, above. In some embodiments, an entity can be aname owner, or a delegate of a name owner, where the term “name owner”generally refers to the user or entity with whom a name is primarilyassociated, and who has registered the name in a given name space.Depending on intellectual property arrangements, a “name owner” may notactually have legal ownership rights to the name, but is still the partywith primary interest in promoting the use of the name to identifyassociated information and services. In some embodiments, generic entitynames such as “zoo” are associated with particular entities via varioustechniques, such as, for example, name auctions. That is, generic namessometimes may have an associated entity.

In some embodiments, the entity representations 1720 can be stored inone or more databases (e.g., one or more directories). Such database(s)can include in a first column entity names, e.g., from a third-partyname space. Thus, first-column entries for the entity name “gimbels” caninclude, for example, “@gimbels” (corresponding to a TWITTER namespace), “fb:gimbels” (corresponding to a FACEBOOK name space), and“.gimbels” (corresponding to a DNS name space). These entries can beincluded in the same entity representation database, separate entityrepresentation databases, or separate tables within one or moredatabases. In embodiments that utilize separate databases or tables foreach name space, the name space identifier may be omitted from thestored entity name, with each database or table instead being identifiedwith a particular name space.

In various embodiments, the entity (e.g., the name owner) may provision,direct, setup, instruct, or otherwise specify to the navigation service1780 the suggestion data 1762 to generate or return for navigation data1751 having certain characteristics, such as having entityidentification (ID) data 1752 (e.g., an entity name) that matches with,maps to, or otherwise corresponds with the entity. In some embodiments,the entity's specifications or instructions in this regard may be storedor otherwise represented in the entity representations 1720 and/oraffect the functioning of the mapping 1782, the mapping 1784, and/or thelookup 1787. In some embodiments, an entity may manipulate the entityrepresentations 1720 and/or the functioning of the mapping 1782, themapping 1784, and/or the lookup 1787 during operation of the navigationservice 1780, such that the suggestion data 1762 and/or the networklocation data 1772 vary frequently. In other embodiments, somethingother than the entity may direct, setup, instruct, or otherwise specifyto the navigation service 1780 the suggestion data 1762 to generate orreturn according to the characteristics of the navigation data 1751. Insome embodiments, the suggestion data 1762 includes or consists of oneor more keywords. Note that a “keyword” can be a concatenated pluralityof separate words, e.g., “shoesonsale”.

In the exemplary depiction of FIG. 17, each row 1731-1734 of the entityrepresentations 1720 contains data representing or associated with adifferent entity. As shown, there can be any number “n” of entitiesrepresented. As shown, the first (leftmost) column of each row includesan identifier for the entity—in this example, row 1731 starts with theentity identifier “Entity 1”; row 1732 starts with the entity identifier“Entity 2”; etc. In some embodiments, the entity identifiers are namesfrom a name space. The next two columns of each row contain any number“m” of suggestions and network locators that are associated with theentity identified in the first column. Thus in this example there is aone-to-many relationship (e.g., 1 to m) between each entity and itsassociated suggestions and network locators.

Items 1735-1737 of FIG. 1 show an expansion or additional details of thelast two columns of row 1734 for “Entity n” 123. Items 1735-1737indicate that there are “m” network locators, and therefore up to “m”network resources, represented for Entity n. As shown, each of items1735-1737 includes one or more suggestions (which may be keywords) inthe left-hand column associated with each network locator in theright-hand column. For example, item 1735 for Entity n 1723 includes oneor more “Suggestion(s)” 1724 for “Network Locator 1” 1725. Thus in thisexample there is a (one-or-more)-to-one relationship (e.g., >=1 to 1)between suggestions and their associated network locators.

In various embodiments, a network locator (e.g. “Network Locator 1”1725) is data sufficient to allow the agent 1710 and/or the user 1705 tolocate a network resource and/or information sufficient to allow theagent 1710 and/or the user 1705 to access the network resource. Examplesof a network locator include a URL, a URI, a URN, an IP address, and aDNS A record, among other things. In various embodiments, a suggestion(e.g., “Suggestion(s)” 1724) is data or code that suggests or otherwisedescribes the network resource that is accessible using the networklocator with which the suggestion is associated. In some embodiments, asuggestion includes, or enables the presentation of, words, images,video, etc. that cause a human (e.g., the user 1705) to be led to, thinkof, consider, or otherwise be reminded of the corresponding networkresource. The suggestions may include applications, includingapplications that are run by the navigation service 1780 to producesuggestion data 1762 and/or applications that are sent in suggestiondata 1762 to be run by the agent 1710. In some embodiments, thesuggestion data 1762 includes or consists of one or more keywords. Oneexample of a suggestion are the characters “gimbels.shoes” inassociation with a network locator that points to a Gimbels retail webpage for purchasing shoes (e.g. the network locator“http://www1.gimbels.com/shop/clothing/shoes”). Another example of asuggestion, in this case a keyword, are the characters “shoes” inassociation with an entity name of “Gimbels” and a network locator thatpoints to a Gimbels retail web page for purchasing shoes.

The term “provisioning” as used herein refers to the collection ofmanagement services by which an entity (e.g., a name owner) creates,updates, and deletes entity representation entries and otherwisemaintains information about name and keyword combinations. Aprovisioning interface may be implemented using a web interface, forexample.

In some embodiments, prior to permitting a name owner to provision itsassociated entity representation data, the name owner may be required toauthenticate itself, and there are many possible techniques for doingso. In some implementations, the name owner demonstrates that it isindeed associated with the entity name in question. This may beaccomplished when first establishing authentication credentials, e.g.,when the name owner signs up for an account with the navigation service.For example, if the name space consists of email addresses, aconfirmation message may be sent to the specified email address. Proofof successful receipt of that confirmation message (e.g., by returnemail or by receiving particular data at a URL in the email message) maydemonstrate ownership of the email address. As another example, if thename space is from one of the social networks (e.g., FACEBOOK), it maybe possible for the name owner to log in to the navigation service usingcredentials from that social network, which may demonstrate ownership ofthe corresponding name. Mechanisms for demonstrating ownership of domainnames are known in the art of domain name management and may be used forprovisioning operations as discussed herein.

Provisioning in the TWITTER name space may be accomplished usingexisting TWITTER authentication techniques. That is, TWITTER itselfauthenticates TWITTER users when they post messages to its service, sotweets automatically carry proof of ownership of the associated name.Thus, a direct tweet to the provisioning operation of the navigationservice may be accepted as an authentic request to update information inthe navigation service's entity representations. For example, a tweet orTwitter “direct message” from “@example_brand” to“@provisioning_operation” of the form “update #news <URL>” may be usedto update the network locator associated with “@example_brand#news” to“<URL>”. Continuing this example, and for some embodiments, no webinterface or email is required, rather, just a tweet directly to theprovisioning operation. The “tweet” channel to the provisioningoperation may also support a broader command set, including setting newentity names, keywords and network locators.

Provisioning in social networks such as FACEBOOK and LINKEDIN may beaccomplished by “sharing” content with certain keywords, viaspecial-purpose applications within the respective environments.

In various embodiments, the entity representations 1720 may beimplemented in any number of ways, including directories, databases,data structures, lookup tables, arrays, records, straight line code,etc., as are known in the computer science art. Also, in variousembodiments, the entity representations 1720 may be implemented as partof the navigation service 1780, as a separate service, in a separatedatabase system, or in various other ways as are known in the computerscience art. The exact implementations are not important to theinvention.

In operation, the embodiment of the system 1700 shown in FIG. 1 mayfunction in the manner described below with respect to a shoe shoppinguse-case example. In this example, the user 1705 is a human who desiresto connect to and interact with a web page for the retailer Gimbels topurchase shoes. To do this, the user 1705 provides input navigation data1751 (also referred to as a “command string”) to the agent 1710, whichdata 1751 generally describes what is desired. The user 1705 can be ahuman or a programmed computer, and the command string 1751 can beobtained by typing into a field, clicking on a link, or speaking into amicrophone. The agent 1710 may have a network locator for the navigationservice hard coded into its software. In some embodiments, the user 1705may type in a character string as input navigation data 1751 to theagent 1710. In a particular example, the user 1705 may type “gimbelsshoes”, “@gimbels!shoes”, “gimbels.shoes”, or “.gimbels!shoes” into thenavigation bar or omnibar of a browser that includes the agent 1710. Theagent 1710 may provide the navigation data 1751 to the navigationservice 1780. Thus, the agent 1710 may process the syntax of thenavigation data 1751 in order to derive a request message, which is sentto the navigation service.

In some embodiments, the agent 1710 may provide the navigation data 1751sequentially as it is entered (e.g., one character at a time). In otherembodiments, the agent 1710 may provide the navigation data 1751 inparts, sections, or other portions, perhaps as distinguished orseparated by specified name space identifiers, delimiters, triggercharacters, symbols, or the like (e.g., period “.”; slash “/”; colon“:”; space “ ”; “@”; “!”; “|”; “fb:”; “in:”; etc. may distinguish oneportion from another). For example, in such embodiments, the input data“gimbels.shoes” may be provided in two parts “gimbels.” and “shoes”based on recognizing the “.” as a delimiter or trigger character. Inother embodiments, the command string “@gimbels!shoes” may be providedto the navigation service 1780 in two parts, as “gimbels” and “shoes”,along with an indication of the associated name space (identified asTWITTER here by the “@” symbol). In other embodiments, the commandstring “@gimbels!shoes” may be provided to the navigation service 1780one character at a time, which the navigation service 1780 accumulatesto form a final command string. In such embodiments, the delimitingcharacters may or may not be conveyed. In yet further embodiments, thecommand string “@gimbels!shoes” may be provided to the navigationservice 1780 in successively more complete parts in multiple iterationsof command strings, with the final version being the full commandstring, e.g., first “@”, then “@g”, then “@gi”, then “@gim”, then“@gimb”, etc. In yet other embodiments, the agent 1710 may provide thenavigation data 1751 only in its entirety to the navigation service1780.

In some embodiments, the agent 1710 may handle the syntax of the commandstring by deriving a query string derived from the entered commandstring and sending it to the navigation service as a request. In suchembodiments, the navigation data 1751 “@example_brand#news” is, forexample, converted to“example_navigation_service.com/lookup?name=%40example_brand&keyword=news”for transmission to the navigation service. (Here, the query string isthe part starting with “?name”. The notation “%40” represents the “@”symbol, which is not allowed in this part of a traditional URL.) Anadvantage of such embodiments is that syntax can continue to evolve, andthat resolution depends only on the availability of a navigation service1780, of which there could be more than one.

In some embodiments, the agent 1710 maps the navigation data 1751directly to a traditional URL with a particular format. For example, thecommand string “@example_brand#news” may be converted to“twitternavigator.net/example_brand/news” for transmission as a requestto the navigation service 1780, or for resolution using traditional DNS(not shown in FIG. 17). The navigation service for such embodimentscould be implemented as the collection of web services corresponding tothe different syntaxes, e.g., one for TWITTER names, one for FACEBOOKnames, etc.

In some embodiments, the agent 1710 determines, based on syntax, whetherentered navigation data 1751 is a traditional URL, in which case theagent 1751 may process it using the traditional DNS system, or a smartnavigation command string, in which case the agent 1719 may process itas disclosed herein.

Other embodiments regarding command string syntax handling are possible,including combination of the above exemplary embodiments, depending onthe type and format of the navigation data 1751.

For embodiments in which the agent 1710 provides an initial portion ofthe command string to the navigation service before the user hascompleted entry of the full command string, the agent 1710 can displaysuggestions for entity names consistent with the already-entered portionof the full entity name. That is, the agent 1710 can convey an initialsegment of the entity name to the navigation service 1780 as the entityname is being entered by the user. The navigation service 1780 canprovide a list of entity names that begin with the same (and/or similar)initial segments of characters to the agent 1710 based on matching theinitial segment to the contents of the entity representations 1720. Theagent can receive the list and display or otherwise present all or someof the contents of the list to the user, such as in a menu, e.g., adrop-down menu. The user 1705 can select a full (or partially complete)entity name presented in the menu in a conventional manner, e.g., byclicking on it. In such embodiments, clicking on a presented entity namecan automatically populate the entry field with the (full or partiallycomplete) entity name as well as any associated name space identifiersymbol. In some embodiments, once this takes place, the agent 1710communicates with the navigation service 1780 to obtain and present tothe user 1705 a list of keywords associated with the selected entityname. This option is discussed further below.

As an example of completing entity names via provided suggestion,consider providing a partial string, “@thenew” to the agent 1710. Theagent, if configured to provide partial data to the navigation service1780, can provide this partial data to the navigation service 1780. Thenavigation service can match the partial string “@thenew” to more thanone entity name, e.g., “@thenewyorktimes” and “@thenewyorkyankees”. Thenavigation service 1780, in turn, can provide suggested completions of“@thenewyorktimes”, “@thenewyorkyankees” and “@thenewyork” to the agent1710. Note that the first two suggestions are of actual entity namesstored by the navigation service 1780, whereas the third suggestion is asuggested partial completion, which can be completed in more than oneway to arrive at a stored entity name. Agent 1710 can present the threesuggested completions to a user 1705, for example, in a pop-up menu. If,on the one hand, the user selects either of the first two suggestions,the process can, for example, present to the user 1705 a list ofkeywords associated with the selected entity name, discussed furtherherein. If, on the other hand, the user selects the third suggestedcompletion, the agent 1710 can communicate the selection to thenavigation service 1780, which can determine that it can be completed byeither of “@thenewyorktimes” or “@thenewyorkyankees”. The navigationservice 1780 can respond by providing these suggestions to the agent1710, which can present them to the user 1705, e.g., in a pop-up menu.At that point, the user 1705 can select either suggestion, and theprocess can continue by, for example, the agent 1710 obtaining from thenavigation service 1780 and providing to the user 1705 suggestedcompletions for a keyword. As discussed in this paragraph, the processof providing entity name suggestions can be interactive in embodimentsthat provide partial data from the agent 1710 to the navigation service1780, in that it can involve multiple interactions before the finalentity name is selected by the user 1705.

Regarding providing entity name suggestions in response to providedentity names, note embodiments are not limited to strict initial segmentcompletion. Thus, for example, if a user were to provide the partialstring “@gimb” to the agent 1710, in some embodiments, the agent 1710and navigation service 1780 can interact and provide to the user 1705the suggested completions of “@gimbels” and “@bimbals” (assuming that“@bimbals” is a provisioned entity name with the navigation service1780). Various known techniques can be used to perform this matching,e.g., limited edit distance detection, etc.

In some embodiments, the agent 1710 provides an indication that anentered (or selected) entity name or entity identification hasassociated keywords and/or suggestions. That is, as a user enters acommand string, the agent 1710 can alert the user upon entry of anentity name that is included in entity representations 1720. Theseembodiments are particularly suitable for implementations in which theagent 1710 provides the navigation data 1751 to the navigation service1780 in parts, sections, or other portions, e.g., providing the entityidentification upon entry of a keyword delimiter. Example indicationsinclude changing the color of the entry field of the agent 1710 (e.g.,changing the background color of a browser omnibar from white to green),issuing an audible alert (e.g., a “beep”), and providing a list ofkeywords that are present in the entity representation 1720 associatedwith the entered entity name. This latter variation can be in the formof presenting a preview page to the user, where the preview pagepresents entity names together with the associated provisioned keywords.

Upon receiving the navigation data 1751, the navigation service 1780 mayprocess the data to classify, split, parse, or otherwise separate thenavigation data 1751 into entity ID data 1752 and supplemental data1753. In some embodiments, the supplemental data 1753 can be one or morekeywords, e.g., prepended with a keyword delimiter character or symbol,such as “!”. In such embodiments, some or all of the suggestions1724-1728 may be keywords. In some embodiments, the navigation data 1751may be separated by the agent 1710 before it is received by thenavigation service 1780. In various embodiments, the entity ID data 1752is data sufficient to allow the navigation service 1780 to attempt toidentify or map to 1782 or otherwise determine at least onecorresponding entity of the entity representations 1720, such as “Entityn” 1723 as represented by arrow 1783 in FIG. 17.

Considering this functionality in the context of continuing the previoususe-case example, the navigation service 1780 may map 1782 the entity IDdata 1752 “gimbels.” to an identifier “.gimbels” in the first column ofentity representations 1720. In this example, the identifier “.gimbels”in the entity representations 1720 is a top level domain controlled bythe registrant retailer Gimbels, and the navigation service 1720 maps“gimbels.” to it because of the exact character string match “gimbels”to “gimbels”, ignoring the trigger character “.”. As another example,for the command string “@gimbels!shoes” from the navigation data 1751,the navigation service 1780 may map the entity name “@gimbels” to theidentifier “@gimbels” in the first column of entity representations1720, accounting for the name space identifier “@”. Variousimplementations may use various other known-in-the-art techniques andalgorithms for mapping entity ID data 1752 to an entity identifier 1723or otherwise identifying one or more entity identifier 1723 thatcorresponds to the entity ID data 1752 in the entity representations1720, in addition to or in place of exact character matching. Inaddition, various implementations may include mapping that is restrictedaccording to context or the identity of the user 1705, for example, inthe case of a user 1705 that is utilizing the agent 1710 in the contextof a mobile device, the navigation service may restrict the mapping 1782and/or 1784 to name spaces (e.g., entity identifiers 1723) and/or tosuggestions (e.g., keywords) 1724 and network locators 1725 that areappropriate for mobile devices (e.g., a network locator 1725 thatcorresponds to the mobile device version of the Gimbels retail web pagefor purchasing shoes). The exact mapping implementation is not criticalto the invention.

Having mapped the entity ID data 1752 to the entity identifier “Entityn” 1723, the navigation service 1780 may next map 1784 the supplementaldata 1753 to one or more suggestions that are associated with the entityidentifier “Entity n” 1723. In various embodiments, the supplementaldata 1753 is data sufficient to allow the navigation service 1780 toattempt to identify or map to 1784 or otherwise determine at least onesuggestion associated with Entity n 1723 that corresponds to thesupplemental data 1753 (e.g., a keyword). In the example shown, thenavigation service 1780 maps the supplemental data 1753 to suggestions1724 and 1728 (e.g., keywords), as represented by arrows 1785 and 1786.As another example, for the entered command string “@gimbels!shoes”, thenavigation service may use the keyword “shoes” as the supplemental data1753; in this example, the keyword “shoes” may map 1784 to thesuggestion 1724 or 1728 “shoes” stored in the entity representation1720, because the keyword string “shoes” and the suggestion string“shoes” exactly match each other.

Considering this functionality in the context of continuing the previoususe-case example, the navigation service 1780 may map 1784 thesupplemental data 1753 “shoes” to a suggestion 1724 “gimbels.shoes”associated with the entity identifier “.gimbels” and may also map thesupplemental data 1753 “shoes” to a suggestion 1728“gimbels.shoes-on-sale” associated with the entity identifier “.gimbels”in entity representations 1720. In some embodiments, the navigationservice 1780 maps 1784 the supplemental data 1753 in the form of one ormore keywords to a suggestion in the form of one or more keywords thatare associated with the already-entered entity name 1723 in the entityrepresentations 1720. Various implementations may use various otherknown-in-the-art techniques and algorithms for mapping 1784 in additionto or in place of partial character matching, which may include mappingthat is restricted according to context or the identity of the user1705. The exact mapping implementation is not critical to the invention.

As shown in the example of FIG. 17, the navigation service 1780 sendsthe mapped-to suggestions 1724 and the mapped-to suggestions 1728 to theagent 1710 as suggestion data 1762. In various embodiments, suggestiondata 1762 is data that represents the mapped-to suggestions in theentity representations 1720 (e.g. suggestions 1724 and suggestions 1728)and that can be presented, digitally, visually, audibly or otherwise, tothe user 1705. As noted previously, in some embodiments the suggestiondata 1762 may include executable code or the like that can be run by theagent 1710. In some embodiments, the suggestion data 1762 may becustomized for presentation by the device hosting the user agent 1710.Continuing the previous use-case example, the navigation service 1780may transmit suggestion data 1762 that includes the string“gimbels.shoes” and the string “gimbels.shoes-on-sale”. (Note thatstrict fragment completion is only one way of suggesting completions forkeywords. Other ways of determining partial matches can also be used.For example, if a user provides “@gimbels!skoes” to an agent 1710,embodiments can match the partial string “!skoes” to “!shoes” usingknown heuristic matching techniques (e.g., limited edit distance).

Upon receiving the suggestion data 1762, the agent 1710 may present thesuggestion data to the user 1705 and enable the user 1705 to choose atleast one of the suggestions (1714). Continuing the use-case example, abrowser implementing the agent 1710 may display the suggestion data 1762“gimbels.shoes” and “gimbels.shoes-on-sale” in a selectable list or dropdown menu that allows the user 1705 to choose one of the suggestionsusing a touchscreen or mouse, as represented by input data 1726. Theprocess can thus be interactive, as with the process of providingsuggested completions for partial entity names. As is known in the userinterface art, an example of one of the many ways a user may select orchoose an item in a selectable list or drop down menu is by positioninga mouse pointer over the desired menu item and clicking the left mousebutton to create input data 1726. There are many other ways andtechniques known in the computer science art for presenting various datachoices and allowing a user to choose or select one or more that may beused to implement 1714, and the exact implementation is not important tothe invention.

In some embodiments, upon entry of a recognized entity name or entityidentification or other name space identification, the agent 1710 canprovide some or all of the list of keyword suggestions that are presentin the entity representation 1720 associated with the entered entityname by providing them to the user in a menu, e.g., a drop-down menu.The user 1705 can select a keyword presented in the menu in aconventional manner, e.g., by clicking on it. In such embodiments,selecting the presented keyword can automatically populate the entryfield with the keyword as well as any associated delimiting character,as well as convey the entered entity name and selected keyword to thenavigation service 1780 as a request (e.g., navigation data 1751). As aspecific example, a user can enter “@gimbels” into an input field of theagent 1710, and the agent 1710 can convey this information to thenavigation service 1780. The navigation service 1780 can respond with alist of associated suggestions (keywords), which the agent 1710 candisplay to the user in a drop-down menu (e.g., containing “shoes”,“men's clothes”, “women's clothes”, etc.) from which the user canselect. Thus, the user is presented with a plurality of suggestedkeywords corresponding to the entered entity name. Further, uponreceiving the list from the navigation service 1780, thus confirming theexistence of an entry for that entity name, the agent 1710 can providean indication that the entity name is recognized by, e.g., changing thecolor of the input field from grey to blue.

Based on the user's input 1726 indicating a choice of the presentedsuggestions, the agent 1710 sends suggestion choice data 1771 to thenavigation service 1780. In various embodiments, the suggestion choicedata 1771 corresponds to one of the suggestions previously sent to theagent 1710 in the suggestion data 1762. In the example of FIG. 17, thenavigation service 1780 uses the suggestion choice data 1771 to look up1787 or otherwise find the corresponding suggestion(s) 1728 in theentity representations 1720, as represented by arrow 1788. Thenavigation service 1780 may then identify the network locatorcorresponding to the looked-up suggestion—in the FIG. 17 example,“Network Locator m” 1729 corresponds to suggestions 1728 because it isstored in the same row—and return the network locator to the agent 1710in the network location data 1772.

In some embodiments, the navigation service 1780 provides the networklocators to the agent 1710 at the same time that it provides thesuggestions (e.g., as part of the suggestion data 1762). In suchembodiments, the agent 1710 need not engage in additional communications(e.g., sending suggestion choice data 1771 and receiving networklocation data 1772) with the navigation client 1780 in order to obtainthe network locator corresponding to the suggestion chosen by the user.However, in some such embodiments, the agent 1710 can send data to thenavigation service 1780 indicating which network locator the userselected.

As stated above, some embodiments can use a mapping that is restrictedaccording to context or the identity of the user 1705. Thus, the agent1710 can utilize 1727 context data, such as network location data 1716,by providing 1772 it to the navigation service 1780. This can be doneautomatically, without requiring user input. The navigation service 1780can use the network location data 1716 to look up 1787 or otherwisedetermine the network locator 1737 that not only corresponds to thematched suggestion(s) 1728 in the entity representations 1720, but alsolies topologically near to the agent 1710 based on the context data.Some embodiments may accomplish this by storing multiple rows thatinclude the same suggestions 1728 paired with different network locatorscorresponding to different geographic or network locations. Note that inalternate embodiments, the navigation service 1780 provides to the agent1710 multiple network locators together with information reflectingtheir geographical or network locations. In such embodiments, the agent1710 can use the context information to select the network locator thatis topologically or geographically closest.

In some embodiments, the context data can be supplied by the agent 1710along with the initial navigation data. For example, the navigationservice 1780 might receive a string for a generic entity name, such as“@zoo”, along with geographical information as part of the navigationdata 1751. The navigation service 1780 might match this entity ID tomultiple entities 1723, and select the one that is closest to theprovided geographical data. In alternate embodiments, the navigationservice 1780 provides multiple network locators to the agent 1710, andthe agent 1710 selects the closest network locator based on its contextdata.

Note that network location data 1716 is but one type of context datausable with embodiments. Other types of context data can include,without limitation, language type, authentication information, IPaddress, reputation data, username/password, encryption schemes,hardware keys, geolocation information, fingerprint identification,encrypted packages using private/public key authentication schemes,machine hardware IDs, product or license IDs, security policycertificates, or any other imaginable user-identifying ormachine-identifying information. These and further examples arediscussed in detail in U.S. patent application Ser. No. 13/828,070entitled “Adaptive Name Resolution” and filed Mar. 14, 2013, thecontents of which are hereby incorporated by reference herein in itsentirety.

Continuing the Gimbels use-case example, if the user 1705 chose“gimbels.shoes” from the drop down menu, then the navigation service1780 may look up 1787 the suggestion “gimbels.shoes” in the entityrepresentations 1720 and find“http://www1.gimbels.com/shop/clothing/shoes” as the correspondingnetwork locator. The navigation service 1780 may then send the string“http://www1.gimbels.com/shop/clothing/shoes” in the network locationdata 1772.

As shown in FIG. 17, the agent 1710 may utilize the network locationdata 1772 for various purposes. In various embodiments, the agent 1710may utilize the network location data 1772 to navigate to, directlyconnect to, interact with, or otherwise access a network resourceaddressed or identified by the network location data 1772. In someembodiments where the network locators 1725-1729 are sent with thesuggestions 1724-1728 in the suggestion data 1762, the agent 1710automatically navigates to, directly connects to, interacts with, orotherwise interacts with the network resource addressed or identified bythe network locator upon the user selecting the correspondingsuggestion, such as a keyword.

Continuing the Gimbels use-case example, the agent 1710 may extract thestring “http://www1.gimbels.com/shop/clothing/shoes” from the networklocation data 1772 and input it into a browser. The browser may resolvethe string as it would any other URL and render the correspondingGimbels web page for the user 1705 to purchase shoes. For example, thebrowser can contact a domain name server to obtain an internet protocoladdress corresponding to the network location data, and then navigate tothat internet protocol address.

To conclude the Gimbels use-case example, the agent 1710, e.g., abrowser, can optionally display the entity name and suggestion (e.g.,keyword) combination. Such display can be in a navigation bar oromnibar. In some embodiments, the agent can display a network locator1725-1729 or the network location data 1772, e.g., a URL, in thenavigation bar or omnibar of a browser. In some embodiments, the agent1710 can toggle between displaying, on the one hand, the entity name andsuggestion (e.g., keyword) combination, and, on the other hand, thenetwork locator or network location data, e.g., a URL. Such toggling canbe initiated by user input, e.g., the user 1705 activating a dedicatedsoft button. Some embodiments display both the entity name andsuggestion (e.g., keyword) combination and the network locator ornetwork location data.

In general, some embodiments may employ redirection. In suchembodiments, once the user 1705 selects or otherwise enters into anagent 1710 a command string that includes entity ID data 1752 (e.g., anentity name, which may include a name space identifier) and supplementaldata 1753 (e.g., a keyword), and the agent 1710 conveys a correspondingrequest to the navigation service 1780, the navigation service 1780 canperform a redirection that utilizes the same special format. Theredirection can be based on the entity name owner's (e.g., name spaceowner) provisioned preferences. The preferences can reflecttime-sensitive or other special concerns. For example, the user mightenter “@gimbels!shoes” into a navigation bar of a browser equipped withan agent 1710. The agent 1710 conveys a corresponding request (e.g., vianavigation data 1751) to the navigation service 1780. The navigationservice 1780 can match or otherwise map the data of the request todifferent data corresponding to a different command string, e.g.,“@gimbels!shoes_on_sale_January_(—)2014”. Such mappings can be specifiedby the name owner itself and be invisible to the user. The navigationservice 1780 can then provide the appropriate corresponding data (e.g.,a network locator 1725-1729) to the agent 1710. This data can beprovided together with data reflecting the original command string(here, “@gimbels!shoes”), so that the redirection is invisible to theuser, or with data reflecting the new command string (here,“@gimbels!shoes_on_sale_January_(—)2014”).

Some embodiments perform error handling in various ways. That is, thenavigation service can respond to requests (e.g., navigation data 1751)that include entity names (e.g., entity ID data 1752) and/or keywords(e.g., supplemental data 1753) that are not in the entityrepresentations 1720 in various ways. If the navigation service 1780receives a request that includes an entity name present in the entityrepresentations 1720 of the navigation service 1780, but the name andkeyword combination is not present, then the navigation service 1780could: return a network locator for an error page, return a networklocator for a related combination of name and keyword, auto-correct to arelated combination of name and keyword, redirect to a relatedcombination of name and keyword, or attempt to find content that mightcorrespond to that keyword but has not yet been registered in the entityrepresentations. The latter four each involve a heuristic determinationof the name owner's (or user's) preferences, using known techniques.According to some embodiments, the navigation service may respond with anetwork locator for a web site corresponding to search results for thekeyword. Such search results may be obtained by a standard search of,e.g., the world wide web, or of a site corresponding to the enteredentity name. Error handling can also provide a way for a name owner toprovision a large set of keywords. The name owner might specify to thenavigation service 1780 that if it receives a request that includes akeyword with certain properties (e.g., SOUNDEX equivalent to a specifiedkeyword, synonym to a specified keyword, etc.), then map it according torules specified by the name owner.

Some embodiments keep track of requests that include an entity namepresent in the entity representations 1720 of the navigation service1780, but where the name and keyword combination is not present. Thenavigation service may collate such requests, e.g., grouping themaccording to entity name, and ordering the requests in each groupaccording to keyword frequency. Such collating may include determiningthe most commonly requested, but unregistered, keywords for each entityname. This information may be provided to a third-party keyword servicesuch that the service may solicit the corresponding name owner toprovision the unregistered keyword(s). The navigation service 1780 mayalso provision example keywords and network locators based on analysisof associated content for a name owner. This may help a name owner getstarted with provisioning network locators for its content.

If the navigation service 1780 receives a request that includes a name(e.g., entity ID data 1752) that does not exist in its entityrepresentations 1720, but that exists in some name space, then, inaddition to the options disclosed above, the navigation service 1780could return a network locator for search results from the name space.For instance, if the user enters “@gimbels!shoes” and “@gimbels” existsin the TWITTER name space, but not in the navigation service's entityrepresentations 1720, then the navigation service could provide anetwork locator for a page of tweets (i.e., TWITTER microblog entries)by “@gimbels” about “shoes”. The page could also include aninformational message offering the name owner the opportunity toregister the keyword with the navigation service 1780. Similar resultpages could be constructed for other name spaces as well.

If the navigation service 1780 receives a request that includes a name(e.g., entity ID data 1752) that exists neither in its entityrepresentations 1720 nor in some other name space, then the navigationservice 1780 could return a network locator for an error page or for asuggestion.

One of ordinary skill will recognize that the components andimplementation details of system 1700 are simplified examples presentedfor conciseness and clarity of explanation. Other components,implementation details, and variations may be used. For example, eitherof suggestion data 1762 and network location data 1772 may include,where appropriate, an error code or other indication that the mapping orlookup has failed or that the direct navigation service 1780 cannotreturn the expected response. Many other variations are possible.

FIG. 18 is a flowchart illustrating a method from the perspective of anavigation service according to various embodiments. The method of FIG.18 can be implemented by a navigation service as disclosed herein. Moreparticularly, the method of FIG. 18 can be performed by the navigationservice 1780 of FIG. 17, or by a URL keyword resolution server describedin Section I, above.

At block 1802 the navigation service receives a request for a networkresource. In some embodiments, the request includes an entity name and akeyword. The request may include a name space identifier, or otherwiseindicate a name space associated with the entity name. The request maybe received from an agent, e.g., agent 1710 of FIG. 17, or from a clientcomputer or from a web browser as disclosed in Section I, above. Theagent may have derived the request from a command string entered by auser as discussed herein. The navigation service may obtain the requestfrom an agent over a network such as the Internet. The navigationservice may receive the request all at once, or in portions, asdisclosed in Section II, above.

At block 1804, the navigation service obtains a uniform resource locatoror other network locator (e.g., one or more of network locators1725-1729) that corresponds to the request received at block 1802. Insome embodiments, the navigation service obtains the uniform resourcelocator from one or more databases or directories, e.g., one or moredatabases containing entity representations, or from one or moredatabases stored in data repository 130 as disclosed in Section I,above. The navigation service can perform a matching between the entityname received at block 1802 and the entity names stored in thedatabase(s), and between the keyword received at block 1802 and thekeywords stored in association with the matched entity name. Thematching of the entity name and/or the keyword can be an exact matching,or utilize heuristics or other fuzzy matching techniques. Once matched,the navigation service retrieves the corresponding uniform resourcelocator (or other network locator) from the database, e.g., from thesame row as the matched entity name and keyword.

At block 1806, the navigation service provides the uniform resourcelocator (or other network locator) to the requestor, e.g., the agent.This can occur by the navigation service sending the uniform resourcelocator to the requestor over a network such as the internet. In someembodiments, the navigation service also provides one or both ofsuggested entity names and suggestions for supplemental data (e.g.,keywords).

FIG. 19 is a flowchart illustrating a method from the perspective of anagent according to various embodiments. The method of FIG. 19 can beimplemented by an agent as disclosed herein. More particularly, themethod of FIG. 19 can be performed by the agent 1710 of FIG. 17, or by aclient computer or in a web browser as disclosed in Section I, above.

At block 1902, the agent receives a command string, e.g., upon a userclicking on a link, or as entered by a user into a field, such as anavigation bar or omnibar. The command string can include an entity nameand a keyword. The command string can further include a name spaceidentifier next to the entity name, and/or a keyword delimiter next tothe keyword.

At block 1904, the agent derives a request for a network resource fromthe command string received at block 1902. The agent can derive therequest by parsing the command string to extract the entity name and thekeyword using known techniques. The request can include the entity name,the keyword, and possibly a name space identifier corresponding to theentity name.

At block 1906, the agent provides the request for the network resourceto a navigation service over a network such as the internet. Thenavigation service can be, e.g., the navigation service 1780 of FIG. 17,or the URL keyword resolution server described in Section I, above. Toconvey the request, the agent may direct it to a uniform resourcelocator or other network locator coded into the agent's software.

At block 1908, the agent obtains a uniform resource locator or othernetwork locator corresponding to the request provided at block 1906. Theagent can obtain the uniform resource locator from the navigationservice, which itself obtains it from one or more databases by finding amatch to the entity name and keyword as disclosed herein. Once the agentobtains the uniform resource locator, it can take actions such asnavigating to the resource identified by the uniform resource locator,for example.

FIG. 21 illustrates an example technique for provisioning a navigationservice according to some embodiments. The provisioning operation issimilar, and in fact can generalize, in some embodiments, theprovisioning shown and described in reference to FIGS. 14-16, above.Thus, FIG. 21 describes provisioning in the context of name-space-basedsmart navigation.

Toward providing context to the technique of FIG. 21, and continuing theexample of “@gimbels!shoes”, presumably, although not necessarily, thename owner, e.g., Gimbels, has a preference for the content to which thecommand string “@gimbels!shoes” should be associated. Furthermore, theuser presumably has an expectation that a keyword such as “shoes” willbe managed directly by a name owner. Accordingly, for this identifier,the name owner may specify the network locator itself.

For other command strings, however, the user may have an expectation—andthe name owner may have a preference—that the keyword would be handledby a third party. For instance, suppose the keyword refers to anothercompany, e.g., Alpha Widgets. The user may expect that identifiers ofthe form “@<name>!alphawidgets” will resolve to resources recommended byAlpha Widgets for a variety of names, for consistency of presentation.Gimbels may likewise prefer to rely on a recommendation by Alpha Widgetsfor the content to be displayed in response to “@gimbels!alphawidgets”.Multiple name owners may therefore choose recommendations or evendelegate authority for identifiers of the form “@<name>!alphawidgets” toAlpha Widgets as a keyword service provider, e.g., as shown anddescribed above in reference to FIG. 14.

As a further example, consider “@gimbels!discount”. Although the generickeyword “discount” would not typically be considered a company name, auser may still expect consistency across multiple names, perhapssupported by a common service provider. A keyword service provider fordiscounts may accordingly assist the name owner in provisioningdirectory entries associated with this keyword. Similar to the“alphawidgets” case, the name owner may choose recommendations and/ordelegate authority for identifiers of the form “@<name>!discount” to thekeyword service provider. However, in contrast to the “alphawidgets”case, if “discount” is not a company name, it would be reasonable forthe navigation service to offer the name owner a choice of more than oneservice provider for these identifiers.

Now suppose that Gimbels takes recommendations for the identifier“@gimbels!discount” from the keyword service provider Acme Discounts (ordelegates authority to that provider). A user may expect that relatedidentifiers will also rely on the same service provider, e.g.,“@gimbels!discounts”, “@gimbels!coupon”, “@gimbels!coupons”, etc.Gimbels subscribe to services from Acme Discounts for these keywords aswell. Another name owner, however, might make a different set ofchoices: “@bigbox!discount” and related identifiers could be delegatedby the example retailer Big Box to keyword service provider BetaDiscounts. Thus, keyword service providers could compete for a nameowner's business.

To summarize, the role of a keyword service provider may be described asfollows:

-   -   A keyword service provider may offer to help a name owner manage        a given keyword;    -   The name owner may choose to accept the help, or not;    -   The help may include a recommended mapping from name+keyword        combination to content, which the name owner may or may not        accept;    -   A name owner may also delegate authority for managing the        mapping to the keyword service provider;    -   A keyword service provider may offer to support multiple        keywords for the same name owner;    -   A keyword service provider may offer to support multiple name        owners (which may or may not be related to one another);    -   A name owner may choose to be supported by multiple keyword        service providers at the same time, for different subsets of        keywords, and may change the set of keyword service providers        over time; and/or    -   A name owner may also choose to be supported by more than one        keyword service provider for the same keyword, for instance if        the resolution of the command string depends on other factors        (e.g., the geolocation of the requester).

It is important to contrast the relationship between the name owner andthe keyword service provider with keyword bidding by search engines. Ina typical keyword bidding process, multiple bidders offer to help thesearch engine handle a search request. The search engine may then awardtop placement of search results to the highest bidder.

In the smart navigation framework, in contrast, multiple keyword serviceproviders offer to help the name owner handle a name and keywordcombination (potentially with other data). The name owner chooses toaccept the help or not, and may change the choice over time. Thenavigation service brokers the relationship between the name owner andthe keyword service providers. The navigation service may also providesummary data about user interest and activity to keyword serviceproviders to introduce them to potential business opportunities (just asit may do for name owners), but the navigation service itself would notdecide which keyword service provider gets the business. Rather, suchdecisions originate with the name owner, and are implemented by thenavigation service on behalf of the name owner.

Note that a name owner is not required to have a keyword serviceprovider for every keyword. By choosing a third-party keyword serviceprovider to support a given keyword, the name owner effectivelydelegates the authority for resolving identifiers involving that keywordto the service provider.

Keyword service providers make it easier for name owners to connect withusers, by improving the user experience when navigating according to agiven keyword. The keyword service provider can potentially becompensated monetarily for this service directly by name owners, orindirectly through the navigation service. In addition, the keywordservice provider, the name owner, or both can compensate the provider ofthe platform (e.g., the browser or application) through which the userinteracts with the navigation service. By including support for keywordservice providers, the navigation service effectively realizes afour-sided market (user/name owner/keyword service provider/platformprovider), giving multiple options for encouraging deployment andmonetizing the capabilities of the navigation service.

Illustrating these considerations by way of FIG. 21, at block 2102, thename owner (e.g., domain name controller) authorizes a keyword service(e.g., third-party) to provision a navigation service (e.g., keywordmanagement server) with provisioning data. The actions of this block mayproceed as described above in reference to blocks 1410-1440 above. Notethat this block, as well as blocks 2104 and 2106, are optional. That is,a name owner may choose to provision its own smart navigation data. Ofcourse, in such embodiments, the name owner performs the actions ofblock 2104.

According to some embodiments, a name owner may provision some data, anda keyword service may provision other data. In some embodiments, thenavigation service initially seeds the entity representations 1720 withkeyword, name, and/or other data. The seeding process may initiallypopulate entity representations 1720, and the name owner maysubsequently alter some or all such data.

At block 2104, the provisioning entity (which may be the name owner)provides keyword and/or other data. The provisioning entity may providesuch information to the navigation service directly, or by way of thename owner. The actions of this block may proceed as described above inreference to block 1450.

At block 2106, the name owner approves of the provided provisioningdata. The actions of this block may proceed as described above inreference to block 1460 of FIG. 14. In embodiments in which the nameowner performs the provisioning itself, this block may be omitted.

At block 2108, the provisioned information is provided to the navigationservice. The provisioned information may be provided by the name owneror by the keyword service. The actions of this block may proceed asdescribed above in reference to block 1460 of FIG. 14.

At block 2110, the navigation service stores the provisionedinformation, e.g., as entity representations 1720 or data stored by thekeyword management server described above in reference to FIG. 14

At block 2112, the navigation service is ready to respond to agentresolution requests, e.g., as shown and described herein in reference toFIGS. 18 and 19.

There are many variations possible with the embodiments disclosedherein. For example, the navigation service is not limited to handlingonly entity name and keyword combinations. Rather, a navigation servicecan handle just an entity name, a combination or two or more entitynames (e.g., forming a hierarchy), or a combination of two or morekeywords (assuming appropriate ownership of at least one of thekeywords), or some other combination. Considering keywords as a namespace defined by a name owner, the navigation service can provide a wayof provisioning and looking up information about a combination of one ormore names, as specified by at least one name owner.

Another variation concerns how the navigation service 1780 is physicallyand logically implemented. In some embodiments, the navigation service1780 may provide multiple instances (e.g., distributed servers) of thelookup operation to increase availability, balancing load across theinstances. Some embodiments may utilize front-end service instances ofthe navigation service 1780 that interface with agents 1710, andback-end instances that hold the entity representation entries, similarin structure to DNS' concepts of recursive and authoritative nameservers. The front-end instances may cache directory entries so thatthey can respond rapidly to requests. In addition, the agent 1710 itselfmay cache entity representation entries. Data integrity and data originauthentication mechanisms such as those in DNSSEC may also be applied.Similar implementation choices may apply to the suggestion andprovisioning operations as well.

Another variation concerns how the agent 1710 handles rendering. Inaddition to displaying the result the user is looking for (as directedby the name owner), the agent 1710 can present additional guidance.Suggestions of names and keywords to enter are one possible form offeedback. The confirmation that the user has entered a recognized orregistered name is another. A user interface associated with abrowser-based agent 1710 may, as disclosed herein, highlight text ordisplay of an icon; it may also play a sound, launch an application,and/or present initial results in a browser window or other interface.In particular, the interaction with the user is not limited to an“address bar” or equivalent. Just as the ultimate web page or othercontent may be rendered outside the interface where the user is directlyentering navigation data, intermediate feedback may also be rendered indifferent programmatic locations.

Another variation concerns alternate alphabets. While this disclosure iswritten with respect to the standard English alphabet, the invention isnot so limited. Embodiments can support other alphabets, including,without limitation, Mandarin (e.g., traditional, simplified), Japanesealphabets (e.g., kanji, hiragana, katakana), Korean, Hindi, Cyrillic,Tagalog, Tamil, Hungarian, Non-English Latin Alphabets (e.g.,Portuguese, Spanish, French), Urdu, Greek, Hebrew, Armenian, Arabic,etc. Both entity names and keywords can be expressed in any, or evencombinations, of various alphabets. For example, the following is avalid syntax for a command string: @

!décoratif, where “

” is an entity name in Chinese and “décoratif” is a keyword in French.Note that in this example, the entity name and keyword are in differentalphabets.

In general, search engines crawl the web in order to retrieve and storesearch results. Search engines can be augmented to search the navigationservice space to identify network locators that have been provisioned.Such search engines can specially identify search results that happen tocorrespond to provisioned network locators. For example, a search enginemight receive a query that it matches to various links. The searchengine may provide these links to a user by way of a results web page.Some of the links may be links provisioned in embodiments by an entity.In this example, the search engine can visually differentiate linksprovided by an entity from the other links, e.g., by presenting them ina different color, font, size, location, etc. As a concrete example thatcontinues an ongoing example presented herein, a user might type“gimbels shoes” into a search engine's query field. The search enginemight provide a results page that includes various links, such as a newsarticle about Gimbels, a blog about shoes, and the linkhttp://www1.gimbels.com/shop/clothing/shoes, which the Gimbels entityprovided to an embodiment, i.e., as a network locator to be associatedwith a command string, e.g., @gimbels!shoes. In this way, the searchspace is extended to incorporate databases from the navigation service.In the results page, this latter link may be distinguished from theothers as discussed herein.

In some implementations, the navigation service returns content ratherthan, or in addition to, network locators. In such implementations, theentity representations 1720 can include extra fields (e.g., one or morecolumns) storing the content in association with the entity name andkeywords. The navigation service can then obtain content (once the userhas selected the corresponding suggestion) by either directly retrievingcontent present in or liked from the appropriate entity representation,or by retrieving content by using the appropriate network locator storedin the entity representation. In either variation, the navigationservice can return the content to the user itself, without the agenthaving to navigate to the associated network locator and retrieve thecontent.

In some implementations, the agent 1710 can utilize an image for all orpart of the navigation data 1751. The image can be in any of a varietyof formats, e.g., bitmap, GIF, JPEG, MPEG, etc. In such embodiments, theimage can be used to generate entity ID data 1752, supplemental data1753, or both, using any of a variety of instrumentalities. For example,the agent 1710 itself, the navigation service 1780, or a separate systemcan obtain the image, either from the agent 1710 or the navigationservice 1780, and convert it to a character string using knowntechniques. The character string can then be provided to the navigationservice, and the process can continue as disclosed herein.

As a concrete example, a user 1705 can obtain an image of a companylogo, e.g., a Gimbels logo in JPEG format. The user can direct the agent1710 to the logo using a graphical user interface, for example. Theagent 1710 can provide the image to the navigation service 1780, whichcan use known image recognition techniques to match the image to thecharacter string “gimbels”. The navigation service can then process thestring “gimbels” as if it had received the string directly, e.g., bymatching it to a provisioned name space identifier and then providing alist of matched keyword suggestions data for the agent to display to theuser.

Note that the use of images is not limited to entity identifications.For example, a user can type “@gimbels” into a field of agent 1710, and,when the agent displays a list of suggestions, the user can direct theagent to an image of a shoe. The agent 1710 can itself recognize theimage using known techniques, or provide the image to the navigationservice 1780 to perform the recognition function. Either way, thenavigation service can respond as if it had received the string“@gimbels!shoes” directly.

Some embodiments utilize paired name space identifier characters and/orpaired keyword delimiter characters, e.g., “[” paired with “]”, “{”paired with “}”, or “(” paired with “)”. In such embodiments, examplesof proper command string syntax can include, for example,{gimbels}(shoes), @gimbels(shoes), {gimbels}shoes, etc.

III. Keyword Parameters

As described in detail herein, in providing a network locator inresponse to received command data (e.g., data that specifies a name andkeyword), a navigation service may take into account other data, such asgeolocation or language (e.g., at 1751 and/or 1771 of FIG. 17). That is,an agent may provide other data together with a name and keywordcombination to a navigation service for resolution. Such other data isnot limited to geolocation and language data. Other data typescontemplated according to some embodiments include, e.g., contextinformation about the requesting agent, context information about theassociated user, other information from the name owner, or other systemstate information. The other data may be provisioned to the navigationservice together with the name, keyword, and network locator data. Asdescribed herein, e.g., in reference to FIG. 14, the provisioning may beperformed by the name owner, the navigation service, and/or athird-party keyword service.

As one example, the identifier “@gimbels!shoes” could be augmented withinformation about shoe brand, type or size. The combined identifiermight then have the form “@gimbels!shoes?mens&running&size=11” (notethat this syntax is only exemplary, and other choices are possible). Thecombined command string may then resolve to content associated with theparticular parameters, e.g., a web page of men's running shoes in size11. The user may interact with the web page and may make further choicesvia conventional web browsing, or the user may modify the command stringor enter a new identifier to navigate to other content.

As another example, the identifier “@gotham!flights” could be augmentedwith departure and arrival times, e.g.,“@gotham!flights?from=metropolis&depart=2014-08-15&return=2014-08-17”.The keyword service provider (e.g., a travel service selected by thename owner of “@gotham”) may provision the navigation service withnetwork locator(s) that resolve to a web page of flight options fromMetropolis to Gotham on August 15, returning August 17. The web page mayprovide further options for the user to select flights.

Although a user could potentially type these combined identifiers as acommand string, e.g., in an omnibar of a web browser, it may not beconvenient for the user to do so. Accordingly, some embodiments utilizean enhanced web browser or other application with which the userinteracts to gather the keyword parameters from the user in acognitively easier way, e.g., by way of a drop-down or pop-up menu suchas those described herein in reference to FIG. 17. For example, when theuser types “@gimbels!shoes”, the browser or application might determineby interacting with the navigation service that this particularidentifier supports keyword parameters. The navigation service maydetermine the type of parameters supported, e.g., shoe brand, type, andsize, or departure city, departure date and return date, and convey suchinformation to the agent. The agent may then present a user interface bywhich the user could enter or otherwise select the parameters, e.g., adrop-down menu of shoe sizes, a text entry box of shoe brands withsuggestions and auto-completion. As one example, the parameters couldalso be entered as free-form or conversational text by the user, forprocessing by the navigation service, e.g., “men 11”, “mens size 11”, or“11 mens” with further interpretation by the service. The browser orapplication may then form the combined command string, including thekeyword parameters based on user selections, and send data derived fromthe command string, i.e., command data, to the navigation service forresolution. The combined identifier could also be copied by the user forembedding in other contexts, e.g., an email message or a tweet.

The user may thus interact with the keyword service provider via anenhanced user interface (e.g., extension to the address bar or omnibaror other data entry field) to provide the keyword parameters. Theinteraction may be customized according to the specific parameters (aswell as the preferences of the name owner and keyword service provider),but it would also be common in certain ways across different serviceproviders so as to increase user familiarity (e.g., dropdown menus andtext entry boxes may have a consistent look and feel). The enhanced userinterface would give the name owner and keyword service provider anadditional, more direct way to engage with users in addition tointerfacing by the web page or other content that the user ultimatelynavigates to. The enhanced user interface for entering or selectingnavigational information, with suggestions, keyword parameters andsimilar features, thus becomes an alternative to the conventionaladdress bar for entering URLs.

Note that such an enhanced user interface remains distinct from the userinterface for interacting with a search engine, however, because theuser is interacting with and according to preferences of the name ownerand keyword service provider, in order to navigate to content associatedwith a specified identifier and any associated parameters, rather thanaccording to preferences of the search engine for the interpretation ofthe entered text.

Because the name owner is, by default, its own keyword service providerfor all keywords that it has not delegated to a third party, keywordparameters can be supported whether or not a third-party provider isinvolved. The “@gimbels!shoes” example is a good illustration. Althoughit is possible that there could be a keyword provider for the “shoes”keyword, for a department store, such information about core productslike shoes may be serviced by the store itself. In the case where thename owner itself services the keywords, the name owner could alsosupport the extended syntax and user interface for keyword parameters.Thus keyword parameters may be considered a part of the smart navigationservice, not limited to the case where third parties are involved in theprocess.

The below Table illustrates a variety of examples of keywords that mightbe supported by a keyword service provider. For brevity, only thesingular form is listed. Plural forms and other variants may be includedas well and may be supported by the same provider according to someembodiments.

TABLE Example Keywords Description career/job Job postingscoupon/discount/saving Discounts and other specials product/buye-Commerce link review/rating/recommendation Ratings and recommendationslocation/map/direction Locations, etc. code/apps Software repositories,applications news/blog Articles, announcements finance Financialinformation, stock quotes photo/image/media/video Various collateralpatents Filed and issued patents flight/hotel Travel informationhome/house/apartment Housing information

According to some embodiments, keywords in the same category may besupported by the same service provider for a given name owner.Furthermore, different name owners may be supported by different serviceproviders even for the same category, facilitating competition amongservice providers (but where the decision is made by the name owner, notthe navigation service).

User behavior may also depend on language. The above Table, for example,includes keywords in the English language. Name owners and users whocommunicate in other languages may converge on different sets ofkeywords. Name owners may also be multilingual, supporting keywords inmultiple languages. Keyword service providers can likewise choose tosupport multiple languages, both for the same and for different nameowners. It is also possible that a keyword with a given spelling mayappear in keyword taxonomies for two or more languages. The keywordmight have the same meaning in these languages, or it might havedifferent meanings. A name owner can accommodate these multiple meaningsby resolving the keyword according to the user's language preferences(in a way similar to the geolocation feature mentioned above). As withother aspects of keyword services for smart navigation, the decision onhow a keyword should be resolved may be ultimately left to the nameowner.

Note that there are two basic approaches to implementing the keywordservice. The first approach is for the keyword service to provide thenavigation service with the information sufficient to obtain a correctnetwork locator from a name and keyword, (and possibly other data). Thesecond approach is for the keyword service to store informationsufficient to obtain a correct network locator from the name and keyword(and possibly other data). Both of these approaches are described indetail below. In what follows, the term “command data” means dataspecifying a name, a keyword, and, possibly, other data.

According to the first approach, the keyword service providesinformation for handling the command data to the navigation service. Insuch embodiments, the navigation service may respond to a clientcomputer's request that includes command data (e.g., as derived from acommand string provided to the client computer) including a keyword, aname, and possibly other data without needing to further communicatewith the keyword service. Instead, once the keyword service provides theinformation to the navigation service, the navigation service may handleclient computer requests directly. In this first approach, a name ownermay authorize the keyword service to provision the navigation servicewith the information sufficient to obtain a correct network locator froma name, keyword, and other data.

Further according to the first approach, there are at least two types ofinformation that the keyword service may provide to the navigationservice for matching a name, keyword and possibly other data to thecorrect network locator. The first type of information is mappinginformation from specific keywords, names, and other data to networklocators. Such mapping information may take the form of triples orquadruples of data, e.g., of the form (name, keyword, network locator),(name, keyword, other data, network_locator), or (name, keyword, [null],network_locator). The navigation service may store such tuples inpersistent memory (e.g., a database) as described in detail herein. Thenavigation service may query the database with the name, keyword, andpossibly other data, to identify the network locator stored in the samerow; that is, the navigation service may correlate the name, keyword,and possibly other data to the corresponding network locator. Note thatthe first type of information may include a plurality of such tuplesprovided to the navigation service by the keyword service, e.g., one foreach combination of name and keyword (and possibly other data).

The second type of information that the keyword service may provide tothe navigation service in order to implement the first approach isresolution logic, e.g., in the form of one or more rules. Such rules mayspecify how to derive a correct network locator from a name, keyword,and other data. The rules may preform a syntactic transformation on thename, keyword, and other data, may perform an information lookup (e.g.,using a database query) on such input data, or may perform a combinationof such procedures. As one example, consider command data provided to anavigation service by a client computer, where the command data includesthe name “gotham”, the keyword “flights”, and other data specifyingdeparture and arrival places and dates. The navigation service may parsethe command data and determine that the specified name and keyword areto be used with a rule that specifies that a network locator beconstructed for a web page that displays flight options for thecorresponding other data.

Note that retrieving stored information is a possible rule element.Accordingly, the second type of information for the first approach maybe considered a generalization of the first type of information for thefirst approach. In other words, a database query (or other form orcorrelation) is an example of a rule.

The second approach for implementing the keyword service is for thekeyword service to store information sufficient to obtain a correctnetwork locator from the command data. According to this approach, aname owner may provide authorization for the navigation service toutilize a keyword service to assist in resolving a name, keyword, and,possibly, other data, to an appropriate network locator. The navigationservice may receive command data including a name and keyword (andpossibly other data) from a client computer. The navigation service mayparse the command data and determine that the keyword service is toresolve the particular request. Such a determination may be made in avariety of ways. For example, the navigation service may utilize thekeyword service for all requests by default. As another example, thenavigation service may store a network locator for the keyword servicein association with the name and keyword, such that when it matches thename and keyword, it retrieves the network locator for the keywordservice.

There are two possibilities for the navigation service once it obtainsthe network locator for the keyword service. The first possibility isfor the navigation service to provide the network locator for thekeyword service to the client computer so that the client computer mayobtain the correct network locator corresponding to the name, keywordand other data from the keyword service using the keyword servicenetwork locator. The navigation service may send to the client thenetwork locator for the keyword service (possibly together with a flagor other indicator specifying that the client computer is to pass thecommand data to the keyword service), and the client computer may form aquery from the command data and send the query to the keyword service toobtain the corresponding correct network locator. The second possibilityis for the navigation service to obtain the correct network locatoritself and then provide it to the client.

For the second possibility, the navigation service may proceed tocontact the keyword service with a corresponding request. That is, thenavigation service may contact the keyword service with a request thatincludes the command data, e.g., a request that includes the name,keyword, and, possibly, other data. Because some keyword services may befor specific words (e.g., “jobs”), in some embodiments, the keyword maybe omitted from the request from the navigation service to the keywordservice, e.g., if the keyword service only handles a single keyword orparticular set of keywords. Once the keyword service receives therequest from the navigation service, it may obtain a correspondingnetwork locator, e.g., in a manner that the navigation service doesaccording to the first approach for implementing keyword parameters asdescribed herein, that is, by way of a lookup operation and/orimplementation of one or more rules.

After the keyword service obtains the appropriate network locator, itmay respond to the navigation service's request in at least two ways.According to the first way, the keyword service may return the networklocator to the navigation service so that the navigation service mayrespond to the client with the network locator. According to the secondway, the keyword service may return the network locator back to theclient directly. For the second approach, the request from thenavigation service to the keyword service may include an identificationof the client so that the keyword service may respond to the clientwithout further interaction with the navigation service.

IV. Computing System Implementations

FIG. 20 is a block diagram of an exemplary computing system or dataprocessing system 2000 that may be used to implement embodimentsconsistent with the invention. Other components and/or arrangements mayalso be used. In some embodiments, computing system 2000 may be used toimplement a navigation service 1780 as shown in FIG. 17, for example,either stand alone or as part of a larger navigation system. In variousembodiments, computing system 2000 may be used to implement an agent1710 as shown in FIG. 17.

Computing system 2000 includes a number of components, such as a centralprocessing unit (CPU) 2005, a memory 2010, input/output (I/O) device(s)2025, and a nonvolatile storage device 2020. System 2000 can beimplemented in various ways. For example, an implementation as anintegrated platform (such as a workstation, server, personal computer,tablet computer, laptop, smart phone, etc.) may comprise CPU 2005,memory 2010, nonvolatile storage 2020, and I/O devices 2025. In such aconfiguration, components 2005, 2010, 2020, and 2025 may connect andcommunicate through a local data bus and may access a database(implemented, for example, as a separate database system) via anexternal I/O connection. I/O component(s) 2025 may connect to externaldevices through a direct communication link (e.g., a hardwired or localwifi connection), through a network, such as a local area network (LAN)or a wide area network (WAN), and/or through other suitable connections.System 2000 may be standalone or it may be a subsystem of a largersystem.

CPU 2005 may be one or more known processing devices, such as amicroprocessor from the Xeon™ family manufactured by the Intel™Corporation of Santa Clara, Calif., or the like. Memory 2010 may be oneor more solid-state storage devices or mediums configured to storeinstructions and information executed or otherwise used by CPU 2005 toperform certain functions, methods, operations, and processes related toembodiments of the present invention. Storage 2020 may be a volatile ornon-volatile, magnetic, semiconductor, tape, optical, or other type ofstorage device or computer-readable storage medium, including devicessuch as CDs and DVDs, meant for long-term storage.

In the illustrated embodiment, memory 2010 contains one or more programsor subprograms 2015, which may be loaded from storage 2020 or from aremote system (not shown), that, when executed by CPU 2005, performvarious operations, procedures, functions, processes, or methodsconsistent with the present invention. Alternatively, CPU 2005 mayexecute one or more programs located remotely from system 2000. Forexample, system 2000 may access one or more remote programs via network2035 that, when executed, perform functions and processes related to orimplementing embodiments of the present invention.

In one embodiment, memory 2010 may include a program(s) 2015 thatimplements the communication, mapping, and look up functions describedwith respect to the navigation service 1780. In another embodiment,memory 2010 may include a program(s) 2015 that implements thecommunication, display, navigation, and connection functions describedwith respect to the navigation service 1780. In yet another embodiment,memory 2010 may include a program(s) 2015 that performs the receiving,obtaining, and providing functions described in reference to FIG. 18. Inyet another embodiment, memory 2010 may include a program(s) 2015 thatperforms the receiving, deriving, providing, and obtaining functionsdescribed in reference to FIG. 19. In some embodiments, memory 2010 mayalso include other programs or applications that implement other methodsand processes that provide ancillary functionality to the invention. Forexample, memory 2010 may include programs that interface with an entityowner or name space owner such that the owner can configure the entityrepresentations 1720 for their entity IDs or name space.

Memory 2010 may be also be configured with other programs (not shown)unrelated to the invention and/or an operating system (not shown) thatperforms several functions well known in the art when executed by CPU2005. By way of example, the operating system may be Microsoft Windows™,Unix™, Linux™, an Apple Computers™ operating system, or other operatingsystem. The choice of operating system, and even to the use of anoperating system, is not critical to the invention.

I/O device(s) 2025 may comprise one or more input/output devices thatallow data to be received and/or transmitted by system 2000. Forexample, I/O device 2025 may include one or more input devices, such asa keyboard, touch screen, mouse, and the like, that enable data to beinput from a user, such as a user 105. Further, I/O device 2025 mayinclude one or more output devices, such as a display screen, CRTmonitor, LCD monitor, plasma display, printer, speaker devices, and thelike, that enable data to be output or presented to a user. I/O device2025 may also include one or more digital and/or analog communicationinput/output devices that allow computing system 2000 to communicate,for example, digitally, with other machines and devices, for example,when computing system 2000 is acting as a web server. Otherconfigurations and/or numbers of input and/or output devices may beincorporated in I/O device 2025.

In the embodiment shown, system 2000 is connected to a network 2035(such as the internet, a cellular network, a private network, a virtualprivate network, or other network), which may in turn be connected tovarious systems and computing machines, such as a desktop computer,smart phone, tablet computer or laptop computer of a user 1705 that isequipped with an agent 1710 or a server computer that is implementing anavigation service 1780. In general, system 2000 may input data fromexternal machines and devices and output data to external machines anddevices via network 2035.

A database 2030 may also be used in conjunction with system 2000. In theembodiment shown, a standalone database external to system 2000 may beused. In other embodiments, a database may be hosted by system 2000. Thedatabase may be used to manage and store data used to implement systemsand methods consistent with the invention. For example, the database2030 may contain the entity representations 1720 of system 1700. Ingeneral, the database 2030 may store information that is accessed and/ormanaged through system 2000. By way of example, such a database may bean Oracle™ database, a Sybase™ database, or other relational database.Systems and methods consistent with the invention, however, are notlimited to separate data structures or databases, or even to the use ofa database or data structure.

It is to be understood that the foregoing description is exemplary andexplanatory only and is not restrictive. In general, systems capable ofperforming the presented techniques may take many different forms.Further variations in configuration and implementation are possible. Forexample, resources described as singular can be plural, and resourcesdescribed as integrated can be distributed. Further, resources describedas multiple or distributed can be combined. The scope of the presentedtechniques is accordingly intended to be limited only by the followingclaims.

What is claimed is:
 1. A method of provisioning a navigation service,the method comprising: receiving, over a computer network, an electronicauthorization to resolve command data comprising a keyword, an entityname associated with a name owner, and other data to at least onenetwork locator using a keyword service, whereby the keyword servicestores in keyword service persistent memory at least one rulecorrelating at least the entity name and the other data to the at leastone network locator; obtaining a network locator for the keywordservice; receiving, over a computer network and from a client computer,command data comprising the entity name and the other data; andproviding, over a computer network, a response to the command data,whereby the client computer obtains the at least one network locator. 2.The method of claim 1, whereby the client computer obtains the at leastone network locator from the navigation service, the method furthercomprising: providing, over a computer network and to the keywordservice, at least the entity name and the other data, whereby thekeyword service correlates the entity name and the other data to the atleast one network locator; and obtaining, over a computer network andfrom the keyword service, the at least one network locator; wherein theproviding, over the computer network, the response to the command data,comprises providing the at least one network locator to the clientcomputer.
 3. The method of claim 1, whereby the client computer obtainsthe at least one network locator from the keyword service, the methodfurther comprising: correlating the entity name and the keyword to thenetwork locator for the keyword service; and wherein the providing, overthe computer network, the response to the command data comprisesproviding the network locator for the keyword service to the clientcomputer; whereby the client computer provides at least the entity nameand the other data to the keyword service, whereby the keyword servicecorrelates the entity name and the other data to the at least onenetwork locator, whereby the client computer receives the at least onenetwork locator from the keyword service.
 4. The method of claim 1,whereby the client obtains the at least one network locator from thekeyword service, wherein the providing, over the computer network, theresponse to the command data comprises providing at least the entityname, the other data, and an identifier of the client computer to thekeyword service, and whereby the keyword service correlates at least theentity name and the other data to the at least one network locator andprovides the at least one network locator to the client computer usingthe identifier of the client computer.
 5. The method of claim 1, whereinthe other data comprises geolocation data.
 6. The method of claim 1,wherein the other data comprises data identifying a language.
 7. Themethod of claim 1, wherein the command data is derived from a commandstring provided to the client computer, the command string consisting ofa name portion and a keyword portion, wherein the name portion comprisesthe name and a name space identifier abutting the name, and wherein thekeyword portion comprises the keyword.
 8. The method of claim 7, whereinthe keyword portion further comprises a keyword delimiter abutting thekeyword, wherein the keyword delimiter is selected from the groupconsisting of: #, !, “.”, $, and |, and wherein the name spaceidentifier is selected from the group consisting of @, fb, in, and “.”.9. The method of claim 7 or 8, whereby the other data is provided to theclient computer through a user interface, wherein the command data isfurther derived from the other data.
 10. The method of claim 1, whereinthe receiving the electronic authorization comprises receiving theelectronic authorization from the name owner or from the keywordservice.
 11. The method of claim 1, wherein the at least one networklocator comprises a uniform resource locator (URL).
 12. The method ofclaim 1, wherein the navigation service is not a domain name system(DNS) service.
 13. The method of claim 1, further comprisingelectronically storing at least one rule in navigation servicepersistent memory correlating an example keyword and the entity name toat least one example network locator.
 14. The method of claim 1, whereinthe at least one rule specifies a database query.
 15. The method ofclaim 1, wherein the at least one rule correlating at least the entityname and the other data to the at least one network locator correlatesthe keyword, the entity name, and the other data to the at least onenetwork locator, and wherein the command data further comprises thekeyword.
 16. A system for provisioning a navigation service, the systemcomprising: at least one navigation service server computercommunicatively coupled to a computer network and configured to receive,over the computer network, an electronic authorization to resolvecommand data comprising a keyword, an entity name associated with a nameowner, and other data to at least one network locator using a keywordservice comprising at least one keyword service server computer, wherebythe keyword service stores in keyword service persistent memory at leastone rule correlating at least the entity name and the other data to theat least one network locator; and an electronic memory configured tostore a network locator for the keyword service; wherein the at leastone navigation service server computer is further configured to receive,over the computer network and from a client computer, command datacomprising the entity name and the other data, and provide, over thecomputer network, a response to the command data, whereby the clientcomputer obtains the at least one network locator.
 17. The system ofclaim 16, whereby the client computer obtains the at least one networklocator from the navigation service, wherein the at least one navigationservice server computer is further configured to: provide, over acomputer network and to the keyword service, at least the entity nameand the other data, whereby the keyword service correlates the entityname and the other data to the at least one network locator; and obtain,over a computer network and from the keyword service, the at least onenetwork locator; wherein the at least one navigation service servercomputer is further configured to provide, over the computer network,the response to the command data by providing the at least one networklocator to the client computer.
 18. The system of claim 16, whereby theclient computer obtains the at least one network locator from thekeyword service, wherein the at least one navigation service servercomputer is further configured to: correlate the entity name and thekeyword to the network locator for the keyword service; and wherein theat least one navigation service server computer is further configured toprovide, over the computer network, the response to the command data byproviding the network locator for the keyword service to the clientcomputer; whereby the client computer provides at least the entity nameand the other data to the keyword service, whereby the keyword servicecorrelates the entity name and the other data to the at least onenetwork locator, whereby the client computer receives the at least onenetwork locator from the keyword service.
 19. The system of claim 16,whereby the client obtains the at least one network locator from thekeyword service, wherein the at least one navigation service servercomputer is further configured to provide, over the computer network,the response to the command data by providing at least the entity name,the other data, and an identifier of the client computer to the keywordservice, whereby the keyword service correlates at least the entity nameand the other data to the at least one network locator and provides theat least one network locator to the client computer using the identifierof the client computer.
 20. The system of claim 16, wherein the otherdata comprises geolocation data.
 21. The system of claim 16, wherein theother data comprises data identifying a language.
 22. The system ofclaim 16, wherein the command data is derived from a command stringprovided to the client computer, the command string consisting of a nameportion and a keyword portion, wherein the name portion comprises thename and a name space identifier abutting the name, and wherein thekeyword portion comprises the keyword.
 23. The system of claim 22,wherein the keyword portion further comprises a keyword delimiterabutting the keyword, wherein the keyword delimiter is selected from thegroup consisting of: #, !, “.”, $, and |, and wherein the name spaceidentifier is selected from the group consisting of @, fb, in, and “.”.24. The system of claim 22 or 23, whereby the other data is provided tothe client computer through a user interface, wherein the command datais further derived from the other data.
 25. The system of claim 16,wherein the at least one navigation service server computer is furtherconfigured to receive the electronic authorization by receiving theelectronic authorization from the name owner or from the keywordservice.
 26. The system of claim 16, wherein the at least one networklocator comprises a uniform resource locator (URL).
 27. The system ofclaim 16, wherein the navigation service is not a domain name system(DNS) service.
 28. The system of claim 16, wherein the at least onenavigation service server computer is further configured to store atleast one rule in navigation service persistent memory correlating anexample keyword and the entity name to at least one example networklocator.
 29. The system of claim 16, wherein the at least one rulespecifies a database query.
 30. The system of claim 16, wherein the atleast one rule correlating at least the entity name and the other datato the at least one network locator correlates the keyword, the entityname, and the other data to the at least one network locator, andwherein the command data further comprises the keyword.